|
|
The following new options were added to MakeTape:
- The ability to write "No Label" tapes was added and
- the ability to select the number of digits
for the file sequence number. The default is 4.
A bug that generated an 18 character Dataset Name for a tape was fixed and a all dataset names are translated to uppercase.
Please visit our online support forum to download our software offerings.
NOTE - The files installed for MakeTape V1.0.0 is significantly different that MakeTape V1.1.0. Therefore, it is highly recommended to uninstall V1.0.0 before installing V1.1.0.
MakeTape is a Windows® program to create virtual tapes (in .AWS format) to be processed by an operating system executing under the Hercules emulator. MakeTape creates virtual Standard or No Label tapes in EBCDIC or ASCII, multiple datasets per tape, each with fixed or variable record formats.
This help file will describe the different options MakeTape has to offer.
Initial Release.
No special options are required.
In a real computer room, a tape must be initialized and mounted on a tape drive before it can be used. This also applies to virtual tapes as well. Virtual tapes are files created on your system's hard drive that can be read by the Hercules emulator.
MakeTape allows you to create a new virtual tape or to reuse an existing virtual tape.
To create a new virtual tape, click on InitTape and
see the dialog box to the right.
Type a volser for the new tape and click on
OK, A volser must be 6 letters or digits. You will then be asked to specify the file name for the
virtual tape (.AWS) file using a standard save box. This will
create the virtual tape but it will not be mounted. .
To mount an existing virtual tape file, click on
File->Mount Tape File. You will then be asked to specify the file name for
the virtual tape (.AWS) file using a standard save box.
Once the tape is mounted, the File Name and VolSer in the Tape Info box will be filled in. This VolSer is written to the VOL1 header record on the tape.
Once the virtual tape is mounted, select File->Input File to specify a file to copy to tape.
The Input File name will fill in after the file is selected.
Unless otherwise noted, it is assumed that the .AWS file is going to processed by an IBM MVS/370 or OS/360 system,
On the top half of the screen, notice the RECFM, Record Size, Mode, Copy, Labels, and Seq Size items. These are used to describe how the tape dataset will be written and what information will be written to the tape.
At this time, only unblocked records are supported.
For fixed length records. each record written to the tape will be LRECL bytes long. Since records are unblocked, BLKSIZE is forced equal to LRECL.
For variable length records, each record written to the tape will be at least 5 bytes long and no longer than LRECL. Note that the 4 byte header for variable length records must be added manually to the LRECL. Since records are unblocked, BLKSIZE is forced equal to LRECL+4. The 4 bytes are for the block length header.
Mode specified is the data from the file should be translated from ASCII to EBCDIC before it written to the "tape". As Is means do not translate before writing the "tape".
Copy specifies if the data should be copied to the tape as records or blocks of data. On the Windows® platform, records are ended by the character sequence "carriage return" "line feed" (X'0C0D'). See below for more information.
The Labels indicates if standard OS labels should be written for each file on the tape. The No Label option allows you to write tapes suitable for systems that don't support standard labels (i.e. DOS/360).
The SeqSize indicates how many digits should be added to the end of the dataset name (i.e. dsn.F0001).
MakeTape starts with all the options defaulted for writing card images to tape (i.e. JCL or program source).
Below is list of characteristics of the PC file and what options to select for MakeTape
| PC File | MakeTape Options |
| Plain text like JCL, source code; can be edited with Notepad or Wordpad (card images). Records are delimited by Windows standard end of line sequence (CRLF) | RECFM=F, LRECL=80, Copy ASCII -> EBCDIC as Records. Records will be padded with spaces, if necessary, to make the record LRECL bytes long. Likewise, records will be truncated to LRECL bytes if too long. |
| Plain text like .TXT or .CSV file. Records are delimited by Windows standard end of line sequence (CRLF) | RECFM=V, LRECL=?, Copy ASCII -> EBCDIC as Records. Records will be truncated to LRECL-4 bytes if too long. |
| ZIP file with no compression. Record delimiters (CRLF) are ignored. | RECFM=F, LRECL=80, Copy ASIS as blocks. Records will be LRECL bytes long with no regard to CR or LF characters. The last record to be written will be padded with spaces, if necessary, to make the record LRECL bytes long. This format is suitable for input to MVSUNZIP. |
| A file that contains binary data (i.e. data already in EBCDIC, such as an object deck or XMIT format file) | RECFM=F, LRECL=80, Copy ASIS, copy Blocks |
To write the file to tape, select the File->Write AWS, The file will now be copied to the virtual tape along with the IBM standard labels.
After the file is copied, the Tape Info will update similar to the following:
![]()
where:
0001 is the physical sequence of the file on the tape.
STAGE0A.JCL.F0001 is the dataset name recorded in the label. This name is derived using up to 11 of the rightmost characters of the PC file name (paths are not included). The full file name on my PC is D:\TURNKEY\SYSGEN\runstage0A.JCL The right most 11 characters are STAGE0A.JCL. The F number is a sequence number label added to each dataset on the tape to make the Dataset Name unique.
LRECL and BLKSIZE are the value recorded in the label.
To access this tape dataset, you will need a DD statement with at least the following::
//DD1 DD DSN=STAGE0A.JCL.F0001,DISP=OLD,
// UNIT=TAPE,VOL=SER=DEMO00
If you want to write additional files to tape, repeat from "Select File To Copy". The label number will increase by 1 for each dataset added to the tape.
When you are done copying files to tape, click on File Demount Tape File. This will write all of the trailer labels and close the virtual tape file.
The virtual tape file is ready for Hercules to access.
If you have any questions or suggestions, please visit our online support forum.