Troubleshooting failed Connection setups

Firstly, evaluate the DCAM Return Code (indicated in the comment line of the CFS mask: R15=X'.....' / R6=X'.....'). A listing of all Return Codes can be found in Appendices A-2/A-3 of the "DCAM Macro Calls" manual. If the DCAM Return Code does not give any information about the cause of the error, go through the following checklist.

UTM Applications:

Was the virtual terminal name given in the OC command?

Try the Connection option ES: OCn appl [, term] [, host],ES

Have the CFS terminal names been added to the KDCROOT (PTERM , LTERM)? (For more information see page 9-)

If the UTM application is on another host, has the correct name of this host been given in the OC command? Has the name of the host from which the CFS task was started been correctly defined in the KDCDEF PTERM statement of the UTM application?

Has the UTM application been loaded? (DCAM-Returncode X'0C4C0000')

DCAM Applications:

Try the OC command with one of the optional parameters ES, or ES1/ES2 (EDIT=DSSIM, simulating a physical screen). These options are important, for example with the VIDEO, TDSPOOL, RDDIA or FTDIA applications.

Try the OC command with optional parameter S (--> OPTCD=(CS,SPEC) ).

Is the application expecting a connection message? A connection message is given in the form O..., MSG=... when a connection is made from a physical terminal. If a connection message is required:

Try the OC command with optional parameter C, and when prompted, enter the connection message. Do not enclose the message in quotes as in the MSG= form.

If a connection message is not permitted (not even the CFS default connection message), e.g. for the DCAM application ROUTE, you may use the option NC (No Connection message).

If none of the above is applicable:

Try the OC command with optional parameter UC (console-type connection).

This is necessary, for example, with UDS database handlers, as well as VM2000 Console (Application $VMCONS).

Has the DCAM application been loaded? (DCAM Return Code X'0C4C0000')

If the OC command is not rejected, but there is also no reply from the application, try pressing the K2 key, then B (break).