IBM 4J The Wait Queue

After a Process successfully completes, it is automatically deleted from the

Execution queue. A flush process command with hold=yes moves a Process from

the Execution queue and places it in the Hold queue. When a session is

interrupted, the Process moves from the Execution queue to the Timer queue if

retry values are specified. If connection is not made before the retry values are

exhausted or if retry values are not specified, the action taken depends on the

conn.retry.exhaust.action parameter.By default, the Process moves to the Hold

queue.

The following table shows the status values for the Execution queue:

Element Comment

PE Pending Execution is the initial queue status

when a Process is submitted with

maxdelay=0.

EX Execution status indicates that the Process is

executing.

The Wait Queue

Processes in the Wait queue are waiting for a new or existing connection to become

available between the local node and the remote node.

Processes can come from the Hold queue or the Timer queue. Processes also can be

placed in the Wait queue by a submit command with no parameters specified,

submit with retain=no, or submit with hold=no.

After the connection is made, Processes automatically move to the Execution

queue.

The following table shows the status values for the Wait queue:

Status Comment

WC This status indicates the Process is ready to

execute as soon as possible, but no session is

available. Other Processes may be executing

with the SNODE, and no other sessions are

available. This Process runs as soon as a

new session is created or an existing session

becomes available.

WR This status indicates that the Process is in

retry status. The number of retries and

intervals between retries is specified in the

network map.

WA This status indicates the initial queue status

when a Process is submitted without a hold

or retain value. This Process is ready to

execute as soon as possible.

WS Thisstatus indicates that the Process is

waiting for the PNODE to continue the

session.

40 Sterling Connect:Direct for UNIX: User Guide

Contents

Main Page Page Page Contents Chapter 1. Controlling and Monitoring Processes..............1 Chapter 2. Process Queuing .....37 Chapter 3. Sterling Connect:Direct Utilities ..............43 Chapter 4. Writing Custom Programs 59 Page Chapter 1. Controlling and Monitoring Processes Overview of the Command Line Interface Starting the CLI Stopping the CLI CLI Commands 2 CLI Job Control CLI History Commands Overview of Sterling Connect:Direct Commands 4 Abbreviations for Common Sterling Connect:Direct Commands Restricting the Scripts and UNIX Commands Users Can Execute Sterling Connect:Direct Command Syntax Generic Parameter Value List Parameter Value Submitting a Process Page 8 Page 10 Page Example - Submit a Process That Runs Every Week The following command submits the Process named payroll: 12 Example - Submit a Process with a Start Time Specified The following command submits the Process named copyfil: Changing Process Parameters The optional parameters for the change process command are the following: 14 Deleting a Process from the TCQ The delete process command removes a nonexecuting Process from the TCQ. 16 The following command deletes all nonexecuting Processes submitted by user ID cduser on node dallas: Removing a Process from the Execution Queue The flush process command has the following optional parameters: The following command flushes all executing Processes named Rome from the Execution queue: The following command flushes all executing Processes on node alma submitted by user ID jones: Stopping Sterling Connect:Direct 18 Viewing a Process in the TCQ 20 Page The following command displays the specified Process number: Monitoring Process Status in the TCQ 22 Page 24 The following command displays a short report for the specified Process number: Output from the command is displayed in the following table: The following command displays a detailed report for the specified Process number: Output from the command is displayed in the following table: Determining the Outcome of a Process 26 Page 28 Page 30 Page Generating a Detailed Output Report for a Process 32 Generating a Summary Report for a Process Running System Diagnostics 34 Page 36 Chapter 2. Process Queuing Overview of the Transmission Control Queue Scheduling Sterling Connect:Direct Activity Progression of a Process Through the TCQ 38 The Execution Queue The Wait Queue 40 The Timer Queue The Hold Queue 42 Chapter 3. Sterling Connect:Direct Utilities Introduction to Translation Tables Creating a Translation Table Compiling a Translation Table Using the ndmxlt Utility 44 The parameters for the ndmxlt command are listed in the following table: ExampleCreating a Translation Table About this task ExampleModifying a Model Translation Table About this task Using Translation During File Transfer Operations Translation Table Error Messages Accessing Sterling Connect:Direct Messages 46 Message File Content Message File Record Format Displaying Message Text Precompressing/Decompressing Files Using the Standalone Batch Compression Utility Special Considerations for Using the Standalone Batch Compression Utility 48 Using the Standalone Batch Compression Utility Following are the parameters for the cdsacomp utility: 50 ExamplePrecompress a Text File ExamplePrecompress a Text File With Codepage Conversion ExamplePrecompress a Binary File ExampleDecompress a Text File Examplescsdacomp Command Help Requesting a summary of cdsacomp command parameters and help options: 52 ExampleDecompress a File on the Remote Node During the Copy Step ExampleSend Precompressed File to z/OS and Storing It as Precompressed Validate Configuration Files Configuration Reports Generating a Configuration Report on the Base Installation 54 Generating a Configuration Report on Sterling Connect:Direct Secure Plus for UNIX The following example shows an excerpt from a sample report: Generating a Configuration Report on Sterling Connect:Direct for SWIFTNet for UNIX 56 Page Page Chapter 4. Writing Custom Programs Introduction to Writing Custom Programs Compiling Custom Programs 60 Writing Custom C Programs Creating a Connection to Sterling Connect:Direct Using ndmapi_connect() or ndmapi_connect_c() 62 Terminating a Connection Using ndmapi_disconnect() or ndmapi_disconnect_c() Receiving Responses Using ndmapi_recvresp() or ndmapi_recvresp_c() 64 Following are the parameters for ndmapi_recvresp() or ndmapi_recvresp_c(): Page 66 The ndmapi_recvresp() or ndmapi_recvresp_c() function has the folliowing return codes: Following is a sample ndmapi_recvresp() function: Sending a Command to Sterling Connect:Direct Using ndmapi_sendcmd() or ndmapi_sendcmd_c() 68 Following are the parameters for ndmapi_sendcmd() or ndmapi_sendcmd_c(): Writing Custom C++ Programs 70 The ConnectDirectSession class methods are described in the following table: Page Following is the ConnectDirectSession class header: 72 Page Page Chapter 5. Writing User Exits User Exit Programs User Exit Functions Initializing Communications with exit_child_init() or exit_child_init_c() 76 The exit_child_init() or exit_child_init_c() function has the following parameter: Waiting for a Message Using recv_exit_msg() or recv_exit_msg_c() Passing a File Descriptor Using send_exit_file() or send_exit_file_c() Sending a Message to Sterling Connect:Direct Using send_exit_msg() or send_exit_msg_c() 78 Overview of User Exit Messages Statistics Exit Message File Open Exit Messages FILE_OPEN_OUTPUT_MSG FILE_OPEN_OUTPUT_REPLY_MSG Security Exit Messages GENERATE_MSG GENERATE_REPLY_MSG VALIDATE_MSG VALIDATE_REPLY_MSG User Exit Stop Message 82 Copy Control Block Exit Log Files Notices 84 Trademarks 86 Index Special characters A C D E I L 88 M N V W