ALLOC.CODES = (allocation errors)
This parameter specifies allocation errors for which IBM® Connect:Direct® retries the Process step as specified in the ALLOC.RETRIES and ALLOC.WAIT initialization parameters. These allocation errors are the Dynamic Allocation Interface Routine (DAIR) codes generated by the dynamic allocation function (SVC99) of the operating system, such as z/OS. The following is an example of an IBM error reason code (0210) shown in the IBM Connect:Direct SDAB005I message.
| SDAB005I - ERR=0210,INFO=0000,REQUESTED DATA SET NOT AVAILABLE. ALLOCATED TO ANOTHER JOB. |
You can find common dynamic allocation error codes in the IBM Connect:Direct MSG file by enclosing the code in the message SDExxxxI skeleton, where xxxx is the error reason code. The variable SDAB005I message short text and description come from the MVS Programming Authorized Assembler Services Guide (general publication number SA22-7608-nn), which is accessible on IBM's website. For ERR codes not found in the IBM Connect:Direct MSG file, see the MVS Programming Authorized Assembler Services Guide.
IBM Connect:Direct defined the following error codes to enable retries for specific failures.
| Value | Description |
|---|---|
| PDSR | This is an internally generated IBM Connect:Direct code, that unlike the others described in this section, is not an allocation code. When two or more Processes attempt to write to the same PDS at the same time, only one can write successfully to the PDS. The remaining Processes have error messages with this PDSR code and are retried in the same way as the other codes discussed in this section. |
| DSNR | This option is similar to the PDSR allocation code but works on non-PDS data sets. When you attempt to send or receive a non-PDS data set, but cannot because the data set is in use, IBM Connect:Direct retries the Process (specified by the retry option) for the number of times specified, if you have coded the DSNR option. |
| GDGR | This option indicates that if the ENQ fails (as described for the GDGENQ parameter) for GDG data sets, the Process is retried. |
| TAPR | This option indicates that a tape Process is retried if the number of tape Processes specified by MAX.TAPE is reached. |
| ARCH | This option indicates that the data set is archived,
and IBM Connect:Direct retries
based upon the value specified for the ALLOC.RETRIES initialization
parameter. You must use the DGAXARCL allocation exit for this option
to work. Note: It is not necessary to use the IBM Connect:Direct DMGALRCL
exit to avoid a common allocation error that ties up the IBM task input/output
table (TIOT) via the enqueue on SYSZIOT. See the discussion on the
sample allocation exit, DGAXARCL (alias of DMGALRCL), in Sample Allocation Exits,
for more detailed information on recall processing of migrated and
archived data sets.
|
Allocation retries are controlled by the PNODE and supported for z/OS and VM/ESA platforms only. The following table lists the default allocation error codes and their meanings.
| Code | Definition |
|---|---|
| 020C | Exclusive use of shared file |
| 0210 | Allocated to another job |
| 0218 | Volume not mounted |
| 0220 | Volume not available |
| 0234 | One device required |
| 0068 | VM minidisk already linked read-only, if transferring with VM |
| 0069 | VM minidisk already linked read-write, if transferring with VM |
| 006A | VM minidisk already linked read-write and read-only, if transferring with VM |
Modifiable through MODIFY INITPARMS command: YES