JESALLOC
Unlike the TSO ALLOCATE command, you can use this command to allocate a subsystem data set even when a JES connect was performed, which occurs when JES is started after the
BMC AMI Ops Automation
subsystem is started.
If the MVS Dynamic Allocate service detects errors, TSO/E generates IKJnnnn messages that are written to the BBI Journal.
Command | Parameters |
|---|---|
JESALLOC | DDNAME [CLASS] [SYSOUT] [DEST(parm | dest,parm)] |
The following table describes the parameters:
Parameter | Function | Notes |
|---|---|---|
DDNAME | Name of the DD statement that is be allocated | The maximum length is eight characters and must conform to the DD name specifications. |
CLASS | Class to be associated with this SYSOUT DD statement. | This parameter is a one-character valid JES output class. Specify an asterisk (*) for the MSGCLASS of the STC. |
SYSOUT | A literal indicating that this DD statement should be allocated to SYSOUT | Code this parameter to be compatible with future extensions to this command. |
DEST | The DEST parameter for DDNAME which can be DEST=parm or DEST=(dest,parm) | See the IBM publication MVS JCL Reference for information about valid values for the dest and parm keywords. |
Condition codes are listed in the following table:
Value | Description |
|---|---|
0 | Command was executed successfully. |
4 | JES rejected the allocation request. |
8 | Not connected to JES (started under MSTR and no JESCNCT card in BBISSP00) |
16 | Syntax error occurred. |
20 | DD name is in use (use TSO free command first). |
This section contains the following topic:
Related topic