Enhanced Console Facility › Restrictions on TSO Commands Processed by the ECF and OSF

Restrictions on TSO Commands Processed by the ECF and OSF

The following restrictions apply to TSO commands or CLISTs executed by the ECF, OSF TSO, OSF TSL, and OSF TSP:

• TGET/TPUT requests are ignored, since the TSO TMP is executed in batch mode.
• Only PUTLINE requests that typically would be printed to the SYSTSPRT file are returned by the ECF and OSF.
• Any GETLINE requests that typically would result in additional input being read from the SYSTSIN file will cause termination of the TSO command or CLIST being executed.
• In the ECF environment, the user PROFILE PREFIX value will not be set to the ID with which the operator logged on. Users of the ECF (OPSECF) facility and the OSF (OPSOSF) facility should run a PROFILE PREFIX(prefix) command before accessing anything but fully qualified data set names.
• LOGOFF commands should not be coded in CLISTs executed through the OSF (OPSOSF) facility. LOGOFF will terminate the OPSOSF address space, which the main CA OPS/MVS address space detects, and then immediately restarts it. If this happens often enough, the CA OPS/MVS address space stops restarting the servers.
• If CLISTs or REXX EXECs will be run through the OSF (OPSOSF) facility that issues long waits, tell CA OPS/MVS to start extra OPSOSF address spaces to make sure there are always some available to process operator and internal CA OPS/MVS requests or preferably schedule these CLISTs/REXX EXECs to run in OSF TSL servers that are intended for this purpose.