IBM OS/390 User Manual
VSE DTFDI
MVS DCB DSORG=PS
DEVADDR = SYSxxx
DDname (in DD statement)
IOAREA1 = xxxxxxxx
BUFNO = 1
or
IOAREA! = xxxxxxxx BUFNO = 2 or more
IOAREA2 = xxxxxxxx
EOFADDR = xxxxxxxx
IOAREA2 = xxxxxxxx
EOFADDR = xxxxxxxx
EODAD = xxxxxxxx
ERROPT = xxxxxxxx
SYNAD = xxxxxxxx
ERROPI = IGNORE
EROPI = ACC
SKIP
SKP
ABE
ABE
MACRF =(G...)
= (p...)
RECFM = FA
= FM
BLKSIZE = nnnn
IOREG = (r)
MACRF = (..L..)
RECSIZE = nnn
LRECL = nn
SEPASMB = YES
User must code the DCB
WLERR = xxxxxxxx
SYNAD = xxxxxxxx
Figure 37. Comparison of DTFDI and DCB macros
13.2.6.9 LIOCS Console File Definition
The DTFCN has no equivalent in MVS because reading and writing via the
console is not handled at the GET/PUT level. MVS provides the WTO macro for
writing on the console and the WTOR macro for writing a message and reading a
reply. Therefore, you must replace a PUT macro for the console by either a WTO
macro to display a message or a WTOR macro for displaying a message and
reading a reply.
console is not handled at the GET/PUT level. MVS provides the WTO macro for
writing on the console and the WTOR macro for writing a message and reading a
reply. Therefore, you must replace a PUT macro for the console by either a WTO
macro to display a message or a WTOR macro for displaying a message and
reading a reply.
Do not display messages on the console unless they are necessary. The system
writes many messages to the operator, and extra messages could lead to
confusion and hinder the performance of the installation.
writes many messages to the operator, and extra messages could lead to
confusion and hinder the performance of the installation.
MVS
WTO
WTOR
WTOR
′
message
′
′
message
′ ,
reply address, reply length, ecbaddress
(2-12)
(2-12)
(2-12)
13.2.6.10 LIOCS Sequential File Definition on Direct Access
Devices
Devices
Devices In VSE and MVS, sequential DASD files are processed in the same way.
OPEN Macro
VSE
OPEN(R)
filename
,...
(r1)
MVS
OPEN
dcbaddress , option1, option2 ,...
(2-12)
304
VSE to OS/390 Migration Workbook