Elixir:

Establish Source and Object Storage PDSs

A PDS (Partitioned Data Set) must be predefined with file characteristics that match the requirements of the generated Elixir code. Datasets can be allocated with Roscoe's DSN facility or with TSO's PDF facility.

If these transfer datasets already exist, then determine the appropriate one(s) to use for your transfer needs.

Source-Type

Source-type laser code members will be those that are suffixed by .FSL, and .JSL.

Example:Typical PDS characteristics for source-type laser code:

DSORG RECFM LRECL BLKSIZE
PO FB 80 4240

Object-Type

Object-type laser code members will be those that are suffixed by .FRM and .JDL. (Fonts are suffixed by .FNT and image files by .IMG)

Example: Typical PDS characteristics for Object-type laser code will be:

DSORG RECFM LRECL BLKSIZE
PO FB 128 4096

NOTE:Regarding Transfering .IMG, .FNT and .FRM Object-type files:

Object-type files must be originally uploaded into a PDS with LRECL=128, then the 128-length records need to be copied to a member on a PDS with an LRECL=129.

You Must USE TSO to COPY the member to a PDS WITH LRECL=129. (a Roscoe IMPort-EXPort will corrupt the record lengths -- even if using "AS IS"!)

DSORG RECFM LRECL BLKSIZE
PO FB 129 4128

EDIT the 129-length member, using TSO ISPF, to put an asterisk '*' in column 129 of EVERY data record.

See Prepare Object-type files for transferring for edit details.

Top

© 2008 by the Rector and Visitors of the University of Virginia.

The information contained on the University of Virginia’s Department of Information Technology and Communication (ITC) website is provided as a public service with the understanding that ITC makes no representations or warranties, either expressed or implied, concerning the accuracy, completeness, reliability or suitability of the information, including warrantees of title, non-infringement of copyright or patent rights of others. These pages are expected to represent the University of Virginia community and the State of Virginia in a professional manner in accordance with the University of Virginia’s Computing Policies.