ASCII

All subsequent labels generated are converted to ASCII before they are wri-
tten. This only affects labels. All data is copied exactly as it is read no matter
the setting of this command.

EBCDIC

All subsequent labels generated are not to be converted before they are wri-
tten. The implication is that the data is still in EBCDIC format. This only affects
labels. All data is copied exactly as it is read no matter the setting of this com-
mand.

VOL1

These commands write 80 byte labels to the tape image. The format of the
labels is controlled by the ASCII and EBCDIC commands. Except for the first 4
bytes of each input line none of the data is checked to make sure it is a valid
tape label. It is up to the user to provide correctly formatted labels as desired.
Essentially the entire 80 byte input record is written to the AWS TAPE image
as is (or converted to ASCII if this flag is set).

HDR1 - HDR2

See VOL1 above.

EOF1 - EOF2

See VOL1 above.

EOV1 - EOV2

See VOL1 above.

UHL1 - UHL8

See VOL1 above.

UTL1 - UTL8

See VOL1 above.

7.2.3 Examples

The following example reads the first dataset from DASD and a second one dataset from tape and writes
them to an AWS format dataset.

//MAKETAPE EXEC PGM=AWSUTIL

//STEPLIB DD DISP=SHR,DSN=my.load.library

//SYSPRINT DD SYSOUT=*

//SYSOUT DD DISP=(,CATLG),SPACE=(TRK,(15,15)),DSN=my.dsname

//INDATA DD DISP=SHR,DSN=my.input.sequential.data

//INTAPE DD DISP=OLD,DNS=my.real.tape.file

//SYSIN DD *

READ INDATA

TAPEMARK

TAPEFILE INTAPE

TAPEMARK

/*

Figure 63: AWSUTIL utility JCL

7.3 RAWSTAPE (Reverse AWSTAPE utility)

The RAWSTAPE program is written by Jan Jaeger and is available on the CBT MVS Utilities Tape
(CBTTAPE) at

7.3.1 Function

The RAWSTAPE utility converts an AWSTAPE file back to a blocked OS dataset such that the original
blocking is restored. As an AWSTAPE file does not contain DCB parameters this utility will not restore the
original DCB parameters, these will have to be added manually with a utility such as IEBGENER.

Upload the AWSTAPE file to OS/390 or z/OS in binary format, do not use CR/LF or any other blocking
feature when doing the file transfer. The file must be uploaded to a RECFM=U dataset, either prealloca-
ted or allocated using IND$FILE. BLKSIZE=4096 is reasonable but any other blocksize will work also.

An AWS tape file can consist of more than 1 file and as such the file number of the tape must be speci-
fied. This file number is equal to the value used when reading a tape with bypass label processing (BLP).
Thus, on a labeled tape file 1 will always be the VOL1 record.

Run RAWSTAPE with SYSUT1 pointing to AWS input file and SYSUT2 to the output file, for example
copying a standalone dump tape.

7.3.2 Examples

The following example copies an AWS tape format dataset back to a blocked OS dataset:

//CONVERT EXEC PGM=RAWSTAPE,PARM=3

//STEPLIB DD DSN=IBMUSER.LOAD,DISP=SHR

//SYSUDUMP DD SYSOUT=*

//SYSUT1 DD DISP=SHR,DSN=IBMUSER.SADUMP.AWS

//SYSUT2 DD DSN=IBMUSER.SADUMP,DISP=(NEW,CATLG),

// UNIT=SYSALLDA,SPACE=(TRK,1200,RLSE)

Figure 64: RAWSTAPE utility JCL

After the previous example the IBMUSER.SADUMP contains the correct data but still has invalid DCB
parameters in the DSCB, these can be corrected with IEBGENER as following:

//SETDCB EXEC PGM=IEBGENER

//SYSPRINT DD SYSOUT=*

//SYSIN DD DUMMY

//SYSUT1 DD DUMMY,DCB=(DSORG=PS,RECFM=FBS,LRECL=4160,BLKSIZE=29120)

//SYSUT2 DD DISP=MOD,DCB=(*.SYSUT1),DSN=IBMUSER.SADUMP

Figure 65: IEBGENER JCL for RAWSTAPE utility