XCOM for AS/400 equivalent of Z/OS TYPE=EXECUTE and TYPE=SCHEDULE

Products

• XCOM Data Transport

Issue/Introduction

When initiating transfers in XCOM for AS/400, is there any functionality equivalent to TYPE=EXECUTE and TYPE=SCHEDULE provided by XCOM for Z/OS?

Resolution

By default, a transfer in AS/400 is executed in the job that runs a transfer command (for example, SENDFILE). This mode of operation would be the equivalent of TYPE=EXECUTE in MVS or also QUEUE=NO in Linux/Unix/Windows platforms.

All transfer commands may specify option ENQ(*YES) which queues the transfer to be processed by the XCOM background process. This mode of operation would be the equivalent of TYPE=SCHEDULE in MVS or QUEUE=YES in Linux/Unix/Windows

Additional Information

In Z/OS, parameter TYPE= is passed to XCOMJOB program in the JCL PARM= field.

• With TYPE=EXECUTE, the transfer is processed entirely by the job step that runs XCOMJOB
• With TYPE=SCHEDULE, a request is posted in the XCOM queue so that the XCOM started task processes the transfer

In Linux/Unix/Window, parameter QUEUE= may be specified in the command line that runs program xcomtcp or in the config file mentioned in the command line. The value specified in the command line overrides whatever is specified in the config file

• With QUEUE=NO, the transfer is executed by the process that runs the xcomtcp command
• With QUEUE=YES, the transfer is posted in the XCOM queue so that is is processed by the xcomd service (in Windows) or the xcomd daemon (in Unix/Linux)