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

7.4 VTTS (Virtual tape transportation system)

The programs presented in this section are part of the VTTS (Virtual tape transportation system) and are
copyrighted and owned by Sam Golob, however the programs on CBTTAPE File #533 can be used
freely. The CBT MVS Utilities Tape (CBTTAPE) can be found at

File #533 of the CBT tape contains the following programs:

7.4.1 Function

The VTT2TAPE program converts AWS-format tape files to real tapes, while the VTT2DISK program
creates an AWS-format virtual tape file from a real tape. The VTT2CNVU program converts a VB-format
AWS-format tape (such as the one produced by the AWSUTIL program) to FB-80 format on MVS so that
VTT2TAPE can be used subsequently to convert the data to a real tape.

The VTT2T2FK program is similar to VTT2DISK except that a real tape is converted to a FAKETAPE (tm)
format tape (see below). VTT2FK2T is similar to VTT2TAPE except that a FAKETAPE tape image, folded
over on MVS into FB-80 format, is converted into a real tape. Unless otherwise mentioned AWS-format
virtual tape files on an MVS system have been folded over into fixed blocked 80-byte record format.
AWS-format files on other systems are just long strings of data.

The FAKETAPE file format is a published interface of Fundamental Software Inc. Fundamental Software
reserves the right to change the format at any time. FAKETAPE and FLEX-ES are registered trademarks
of Fundamental Software Inc.

The AWS Tape format is produced by IBM's P/390 and Hercules systems to create disk files which an
MVS system reads and writes as if they were actual tapes. Another name for these disk files is "virtual
tapes", as the MVS system looking at these files "thinks" that they really are tapes.

There are programs like AWSUTIL which can read real tapes and create virtual tapes from them. These
virtual tapes can be loaded on a Hercules system somewhere and be read as a tape.

VTT2DISK performs this function also, by reading a real tape and producing an FB-80 folded AWS-format
tape as an MVS disk file. While reading the tape the VTT2DISK program produces a lot of statistics about
the tape. The advantage of the VTT2DISK program is that it can be run on mainframe-based MVS sys-
tems that cannot normally produce AWS-format virtual tapes.

Another issue is encountered when transferring data in the other direction. Suppose you have an MVS
system that cannot read a tape in AWS format. Most MVS systems which are not P/390 or Hercules
machines are in this position. For these you have to convert an AWS virtual tape disk file to some format
that the MVS system can convert into a REAL tape. That is the purpose of the VTT2TAPE program.

7.4.2 Control Statements

The VTT2DISK program allows the following keywords via the SYSIN DD Statement:

CHUNKSIZE=nnnn

This specifies the chunksize. Any chunksize up to the limit of 65535 bytes is
allowed. If not specified the default is 65535 bytes.

NEWVOL=volser

This keyword changes the VOLSER on VOL1 label to volser.

READ

The READ keyword produces a read only run, no AWSOUT is created.