Follow these steps to implement DFSMSrmm disposition processing.
- When you plan on using disposition control files to trigger sticky
label production, define disposition control information in a disposition
control file as described in Modifying the contents of the disposition control file. You can define
separate disposition control files for individual users, a separate
job, or a separate job step. Define the data sets with LRECL 80. The
data sets can be sequential files or can be members of a partitioned
data set. You can also include data in your JCL stream instead of
defining a data set.
- When you do not plan to use disposition control files, but you
would still like to create sticky labels, you must customize the
supplied EDGUX100 exit module. You can use the default label prepared
by DFSMSrmm, or do your own custom label processing.
- Add the disposition control file DD name to the batch job step
of the tape jobs that process the tape files for which messages or
labels or location assignment is required. The DD name is the same
name as you specified in DISPDDNAME in parmlib.
- Define the disposition control file DD name in the DFSMSrmm EDGRMMxx parmlib
member by using the OPTION command DISPDDNAME operand as described
in Defining system options: OPTION. When you plan on using disposition control
files, you can also define a message ID in parmlib by using the OPTION
command DISPMSGID operand. DFSMSrmm builds a WTO message by using
the message number from the DISPMSGID parmlib option and the message
text defined in the disposition control file.
- If you do not add the OUTPUT JCL statement, sticky labels are
produced using a WTO on route code 13. Add the OUTPUT JCL statement
to the DFRMM started procedure as shown in Step 8: Updating the procedure library if
you want DFSMSrmm to dynamically allocate a SYSOUT file for each label.
Use the attributes of the OUTPUT statement to define how the label
output should be printed.
- Document the procedures you use for printing label output and
applying sticky labels to the correct volumes. If you are using DFSMSrmm
disposition control for the first time, work with your operations
staff to develop, test, and document procedures for responding to
DFSMSrmm messages, printing labels, and using the EDG_EXIT100 exit
to modify output. See z/OS DFSMSrmm Managing and Using Removable Media for
information about procedures for your operators.
Tip: DFSMSrmm disposition processing can
fail when your application closes a DASD data set and a tape data
set at the same time. The system issues error code 50D under these
conditions.
- When the DASD data set was allocated with RLSE for the SPACE parameter
in the DD statement or RELEASE in the TSO ALLOCATE command,
- When the SMS management class specifies YI or CI for the partial
release attribute.
Partial release processing during CLOSE holds an exclusive enqueue
on the task input/output table (SYSZTIOT) resource and can prevent
DFSMSrmm from opening the disposition control file at the same time.
To ensure that the disposition control file can be opened, code a
separate CLOSE for every data set or remove the RLSE parameter from
the DD statement for the DASD data set.