Starting a Task on a Remote Logical Unit
Non-LU6.2 Sessions
idmscu19
Non-LU6.2 Sessions
For non-LU6.2 sessions
, if the UIOTASK field in the UIOCB contains a task name (is nonzero and nonblank) when a #TREQ ALLOC is issued, CA IDMS/DC will automatically send the task code to the remote system immediately after the session is established.LU6.2 Sessions
For LU6.2 sessions
, if the UIOTASK field in the UIOCB contains a task name (is nonzero and nonblank) when a #TREQ ALLOC is issued, CA IDMS/DC will automatically send the LU6.2 allocate request to the remote system, requesting the remote system to start the named task.Requests from Remote Units
When CA IDMS/DC receives an allocate request from a remote LU6.2, it does the following:
- If the allocate request contains a nonzero and nonblank value in the user id (UIOUSER) or password (UIOPASS) fields, CA IDMS/DC will run the signon task for that session.
- The task identified in the allocate request is then attached.
- The conversation type (UIOCONV) and sync-level (UIOSYNC) are also passed by the allocate request and moved into the UIOCB.
Any errors encountered while processing a remote allocation request, for example, task-not-defined or security violations, are reported to the remote system through an SNA sense code.
For more information about sense codes, see Error Handling in this section.