You identify the input disposition control file by using DFSMSrmm
EDGRMM
xx parmlib DISPDDNAME operand. The disposition control
file is a fixed format sequential file with a record length of 80
characters. All the parameters including the message text are position
dependent.
Figure 1 shows the layout for the disposition
control file.
Figure 1. Disposition control file record formatddname_1nrlOUT=vvvv,message text
ddname_1nrlmessage text
ddname_2nrlLOC=vvvvvvvv,message text
ddname_3nrlLOC=vvvvvvv,message text
- ddname
- 1-to-8 character ddname of an input file or output file. This ddname must
match the ddname you defined for the input tape file or the output
tape file processed by the current job step. DFSMSrmm only processes
the statements that match to the DD name of the file being processed
by CLOSE or EOV.
You can code multiple lines for each ddname specified
and can include as many different ddnames as is required to cover
tape data sets requiring disposition support. As each file is processed
by CLOSE or EOV, DFSMSrmm uses only those statements that match the
ddname of that file. ddname must be coded in position 1 through
8.
- n
- Code any non-blank character in position 9 to cause the message
to be issued in a non-roll deletable message to the console.
- r
- Code a character to define the route code to use for the WTO.
Use one of the characters shown in Table 1 to use
specific route codes. Use any character other than the characters
in Table 1 to use the default route code 13.
Table 1. Setting the message route codeIf You Code |
Then You Are Requesting This Route
Code |
---|
Any |
13 (default value). Any value other than those
results in the default value being used. |
A |
2 |
B |
3 |
C |
5 |
* |
11 |
F |
2,11 |
G |
3,11 |
H |
5,11 |
- l
- Indicates if a sticky label is to be produced as part of disposition
processing and must be coded in position 11. DFSMSrmm ignores any
other value and no label is produced. The valid text codes are shown
in Table 2.
Table 2. Coding sticky label textIf You Code |
Then You Are Requesting That |
---|
L |
a label is produced by disposition processing.
You can code multiple L's with the same ddname and route code if more
message text is required. |
M |
a label is produced by disposition processing
but the message text is passed as user data to the EDG_EXIT100 installation
exit for further processing. |
- OUT=vvvvvvvv
- This is an optional keyword starting in position 12. Use OUT
to change the location for a volume. When you use OUT to change a
volume's location, you do not need to confirm the volume move. When
OUT is specified, OUT must be followed by a comma, if you also specified
message text. vvvvvvvv is a 1 to 8 character location name,
that is to be used by DFSMSrmm as a location name for the current
volume.
- LOC=vvvvvvvv
- This is an optional keyword. If you specify LOC, it must be
followed by a comma if the optional message text is specified. vvvvvvvv is
a 1 to 8 character location name. DFSMSrmm uses the value as a location
name for the current volume. When you use LOC=, you request that DFSMSrmm
update the volume's' destination so that the move can be tracked and
confirmed later.
LOC and OUT are mutually exclusive. If you specify
multiple statements for the same DD name, DFSMSrmm uses the last location
name that you specify for the volume.
You can optionally blank
pad location names on the right up to the maximum length of a location
name.
DFSMSrmm checks the location name you specify against
the location names you defined using the DFSMSrmm LOCDEF location
information defined to DFSMSrmm at startup time. If the location you
specified, is not defined using LOCDEF DFSMSrmm treats the location
as if it is a loan location. If the location you specified is identified
as a storage location, use OUT= if you do not want to confirm the
move. Use LOC= if you want the move confirmed at a later time.
You
can use EDG_EXIT100 to control how the location name is used as described
in Changing location information with EDG_EXIT100. You can override the location type determined
from the LOCDEF location information to specify that a location is
a loan location. You can control whether a confirm move is required
for DFSMSrmm storage locations.
When you specify a location
name, DFSMSrmm uses this information just as if you had entered the
value on an RMM CHANGEVOLUME subcommand with either LOANLOC or LOCATION.
If the location is a bin-managed storage location, the required location
is set to this value and inventory management DSTORE processing assigns
a bin number. You can override any location assignment by defining
vital record specification movement policies.
- message_text
- This is up to 69 characters of message text to be issued as
a WTO. It must begin in position 12 or after the comma which separates
the message text from the location name. If additional text is required,
include another record in the control file specifying the same ddname
and route code. Each message is issued as a separate WTO.
If the l value
is M, the message text is limited to up to 69 characters of text and
is treated as user data for label processing. No additional ddname
records are supported for the M user data option.
Figure 2 shows the sample JCL, if you want to perform
these tasks:
- Issue a WTO on route code 2 and route code 1
- Generate a sticky label
- Set the volume location to a location called FICH
- Confirm that the volume is moved to the location FICH. In Figure 2, when IEBGENER closes the SYSUT2 output file, DFSMSrmm
scans the DISPDD file for the SYSUT2 DD statement, if the DISPDD
file is defined. Figure 2 shows two entries for SYSUT2,
which is the file being closed. The first entry requests that DFSMSrmm
issue the message 'SEND THIS TAPE TO THE FICHE PRINTER' on route
codes 2 and 11, that a sticky label is generated, and that the volume's
move to location FICH is already confirmed. The second entry provides
user data that is passed to the EDG_EXIT100 installation exit. DFSMSrmm
includes the user data in the sticky label it generates as described
in Creating sticky labels
Figure 2. Sample JCL to request disposition processing// EXEC PGM=IEBGENER
//SYSUT2 DD DISP=(,KEEP),DSN=MY.FICHE.DATA,UNIT=TAPE,LABEL=(,SL)
//SYSUT1 DD DISP=SHR,DSN=MASTER.FICHE.DATA
//SYSIN DD DUMMY
//DISPDD DD *
SYSUT2 FLOUT=FICH,SEND THIS TAPE TO THE FICHE PRINTER
SYSUT2 MUSER DATA TO BE SENT TO EDGUX100
/*
The message DFSMSrmm issues is EDG4054I, but you can use the DISPMSGID
parmlib option to change the message number to an installation selected
value.