
Coding the Label Print Subroutine Introduction
Chapter. 6 Additional BIM-EPIC Utilities 6-45
Coding the Label Print Subroutine
Introduction
You can use BIM-EPIC to create gummed dataset labels for output tapes automatically. A
BIM-EPIC program gathers information about a tape dataset when it is opened. You write a
subroutine that formats the information and prints the label.
When an output tape dataset is opened, BIM-EPIC creates the following 58-byte record:
Field Length
Dataset name 17 bytes
Volume serial number 6 bytes
Job name 8 bytes
Partition ID 2 bytes
Date 8 bytes (mm/dd/yy)
Time 6 bytes (hhmmss)
Tape device number (cuu) 3 bytes
Density 2 bytes (C0, C8, D0, and so on)
CPUID 4 bytes (binary)
Tape volume sequence 2 bytes (binary)
BIM-EPIC then passes the record and control to your subroutine. Your subroutine formats
and prints the label, and then passes control back to BIM-EPIC.
You can print labels from CICS or in batch mode. Printing dataset labels in batch mode
requires a dedicated printer and, of course, a dedicated partition. To print dataset labels
online requires a dedicated printer and a dedicated terminal unless you start the transaction
through the PLT. If you start the transaction through the PLT, you must dedicate a printer
port to the transaction. That printer port can be freed by deleting the transaction from the PLT
or by entering the TPRE transaction in CICS.
The RMNTPRT configuration option must be set to YES.
You can write your subroutine in either COBOL or Assembler. You can use the copybook
record layout TSIDBPR.C or TSIDPRT.A. Sample Assembler and COBOL subroutines are
provided to demostrate the coding technique required to print tape labels in a batch partition.
These programs can be found in the BIM-EPIC installation library under the names
TSIDPR.C and TSIDPR.A (COBOL and Assembler respectively). Both Assembler and
COBOL subroutines should open the printer file (DTF) only once to avoid depletion of
Partition GETVIS. The COBOL subroutine program ID must be TSIDPR to avoid a conflict
with the entry point name which must be defined as TSIDPR1.
Description
Overview
Comentarios a estos manuales