CMS/DOS does not support the FEOVD, HOLD, and LABADDR operands of the DTFSD macro. Figure 40 describes the operands of the DTFSD macro and
their support under CMS/DOS. An asterisk (*) in the status column
indicates that CMS/DOS support differs from DOS/VS support. rj-----------------------------------------------------------------------------, I Operand IStatus! 1-------------------------------------------------------------------------- IBLKSIZE=nnnn ILength of one I/O area, in bytes.
1--------------------------------------------------------------------- I EOFADDR=xxxxxxxx
IOAREA1=xxxxxxxx CONTROL=YES DELETFL=NO
* DEVADDR=SYSnnn * DEVICE=nnnn * ERREXT=YES ERROPT=xxxxxxxx IName of your end-of-file routine. IName of first I/O area. ICNTRL macro used for this file. IIf DELETFL=NO is specified, the work file I is not erased. Otherwise, when the work 1 file is closed, CMS/EOS erases it. ISymbolic unit. This operand is optional. If 1 DEVADDR is not specified, all I/O requests 1 are directed to the logical unit identified I on the corresponding CMS/DOS DLBL command. 1 IIf a valid logical unit is specified with
t the DEVADDR operand of the DTF and a 1 different, but also valid, logical unit is I specified on the DLBL command, the unit I spectfied on the DLBL command overrides the I unit specified in the DTF. However, CMS/DOS 1 issues an error message if a valid logical I unit is specified in the DTF and no logical 1 unit is specified on the corresponding DLBL I command.
(2314, 3330, 3330-11, 3340, 3350). If omitted, 2311 is the default used at
compilation time. At execution time, when
when the CMS/DOS $$BOPEN routine is
opening a DTFSD work file, the device code
in the DTF corresponds to the device code
of the device to which the logical unit is
assigned.
All DTFSD output files and DTFSD input
files that reside on CMS disks are handled
in the same manner. This device code cannot
be overridden by the compilers. You must specify the EEVICE=nnnn operand
correctly for input files residing on DOS disks; otherwise, CMS/DOS issues an error. IAdditional error facilities and ERET are I desired. Specify ERROPT. I (IGNORE, SKIP, or name of error routine).
Prevents job termination on error records.
Do not use SKIP for output files.
Figure 40. CMS/DOS Support of DTFSD Macro (Part 1 of 3) 302 IBM VM/370 System Programmer's Guide
r-----.--------------------------------------------------------------------, Operand I IFEOVD=YES HOLD=YES IOAREA2=xxxxxxxx IOREG= (nn)
LABADDR=xxxxxXXX
MODNAME=xxxxxxxx NOTEPNT=xxxxxxxx RDONLY==YES RECFORM=xxxxxx RECSIZE=nnnnn SEPASMB=YES TRUNCS=YES TYPEFLE=xxxxxX IUPDATE=YES IStatusl Description
*
*
*
t Not -supported. jNot supported. HOLD=YES is specified for DTFSD update or work files to provide a
track hold capability. However, the CMS/DOS open routine sets the track hold bit off
and bypasses track hold processing. IIf two I/O areas are used, name of second I area. IRegister number. Use only if GET or PUT I does not specify work area or if two I/O I areas are used. Omit wORKA. INot supported. IName of SDMODxx logic module for this DTF. I If omitted, IOCS generates standard name. I (YES or POINTRW). YES if NOTE,POINTR,POINTW, I POINTS used. POINTRW if only NOTE,POINTR, I POINTW used.
jGenerates a read-only module. Requires a I module save area for each routine using I the module. (FIXUNB, FIXBLK, VARUNE, SPNUNB, SPNBLK, VARBLK, or UNDEF). If omitted, FIXUNB is
assumed.
For work files use FIXUNB or UNDEF. Although
work files contain fixed-length unblocked
records, the CMS file system handles work
files as variable-length record files. If
you specify FIXBLK or FIXUNE when creating
a eMS file on a CMS disk, CMS writes the
file in variable-length format. The
LISTFILE command would show the file as V format. IIf RECFORM=FIXBLK, number of characters in I record. If RECFORM=SPNUNB. SPNBLK. or I UNDEF, register number. Not required for lather records. IDTFSD is to be assembled separately. IRECFORM=FIXBLK or TRUNC macro used for this I file.
i (INPUI, OUTPUT, or WORK). I is assumed.
If omitted, Tl.TnTTT IInput file or work file is to be updated. Figure 40. CMS/DOS Support of DTFSD Macro (Part 2 of 3) Part 3. Conversational Monitor System (CMS) 303
Previous Page Next Page