If your TPs start or stop the APPC subsystem or change the
number of active sessions programmatically, you must change them
to run on the Node Type 2.1 version of LU 6.2 API/XL. On the Node
Type 2.1 version, TPs cannot call the MPE COMMAND intrinsic to issue APPCCONTROL commands programmatically, because APPCCONTROL commands are not interpreted by the MPE command interpreter.
A command interpreter for APPCCONTROL commands is installed with the Node Type 2.1 version
of LU 6.2 API/XL. A system UDC file, which is installed with the
product, translates APPCCONTROL commands into MPE RUN commands that invoke the APPCCONTROL command interpreter.
Control Operator Intrinsics |
 |
If you want to start or stop the APPC subsystem or change
the number of active sessions programmatically, Hewlett-Packard
recommends that you use the control operator intrinsics instead
of APPCCONTROL commands in your transaction programs. Unlike APPCCONTROL commands, control operator intrinsics will return status
information to programs that call them. The control operator intrinsics
are documented in the APPC Subsystem on MPE XL Node Manager's Guide.
MPE HPCICOMMAND Intrinsic |
|
If necessary, you can still issue APPCCONTROL commands programmatically. However, because APPCCONTROL commands are implemented with UDCs, you must use the
MPE HPCICOMMAND intrinsic instead of the COMMAND intrinsic. See the MPE XL Intrinsics Reference Manual.
TRACEON Parameter of APPCCONTROL START |
|
If your TPs issue the APPCCONTROL START command, you cannot specify the TRACEOFF parameter, because it is not supported on the Node
Type 2.1 version of LU 6.2 API/XL. On the Node Type 2.1 version,
APPC subsystem internal tracing is turned off by default, and the TRACEON parameter of the APPCCONTROL START command turns it on at subsystem startup. You must remove
the TRACEOFF parameter of the APPCCONTROL START command from all transaction programs and job streams.
