The AID chain
The AID chain is used for tasks that are due to start immediately. Tasks are moved from the ICE chain to the AID chain as soon as the scheduled time expires, and they are placed there directly if there is no time delay requested.
If a task needs a resource, usually a terminal, that is unavailable, the task remains on the AID chain until it can use the resource.
AIDs are addressed from system entries with their forward and backward chain pointers at offset '0C' and '10' respectively. AIDs contain the following fields that can be useful in debugging.
- AIDTYPE (X'2D')
- Type of aid:
Content Offset Meaning AIDBMS X'80' BMS AID AIDPUT X'50' Start with data AIDINT X'40' Start with no data AIDTDP X'10' Transient data AID AIDISC X'08' Queued allocate type AID AIDCRRD X'04' Remote delete type AID - AIDSTATI (X'2E')
- AID status indicator:
Content Offset Meaning AIDPRIV X'80' Privileged allocate AIDSENT X'40' This has been sent to the TOR by CRSR AIDCANCL X'20' Cancel this AID AIDROUTP X'10' Not yet routed to the AOR AIDSHIPD X'08' Prevent duplicate send AIDREMX X'04' AID for a remote transaction AIDREMT X'02' AID for a remote terminal AIDSTTSK X'01' Task already initiated - AID_TOR_NETNAME (X'65')
- Netname of the owning region for a specific terminal
- AID_TERMINAL_NETNAME (X'5D')
- Netname of terminal
- AIDDATID (X'34')
- TS queue name holding the data.
- AID_REROUTED (X'4E')
- AID rerouted to a different TOR
You can see the AIDs in the TCP section of the formatted system dump. Look in field AIDTRNID (the 4-character transaction ID) of each AID, to see if it relates to your task.
If you do find an AID that relates to your task, your task is scheduled to start, but cannot do so because the terminal is unavailable. Look in field AIDTRMID to find the symbolic ID of the terminal, and then investigate why the terminal is not available. One possibility is that the terminal is not in ATI status, because ATI(YES) has not been specified for it in the TYPETERM definition.