Elixir:

Download Existing Laser Code Member for Modification

Modifications can be made to pre-existing laser code members by downloading the code from its master storage PDS on the Enterprise Server to the Elixir workstation PC, and then using it as input to Elixir.

Note: The following instructions were written based on using the Elixir workstation and McGill 3.14.

Using TSO's PDF (ISPF-Transfer Facility)

  1. Sign onto TSO, using a Mercury-McGill 3.14 session of MOD2 Terminal type (24 X 80 size).
  2. Select menu option P (ISPF/Program Development Facility) .
  3. Select item #6 Command.
  4. With your mouse, click on the session's tool-bar to select Transfer.
  5. Then select Receive (download) option.

  6. Fill in the Download from HOST NAME with the source PDS name and member name that reside on the Enterprise Server.

    Note: Be sure to place single quotes around the host name, such as:

    'Z01AF.DEV.OBXXX128(MEMNAME)'
    'Z01AF.DEV.SRCEXXX(MEMNAME)'

    You can use either an Object-type member, or a Source-type member as input into the Elixir converter

  7. For Download to: select Disk.
  8. Select TSO as the HOST SYSTEM.
  9. Under General Options, use attributes ASCII, CRLF for (80-byte) TEXT type transfers; or turn off ASCII & CRLF to imply BINARY for (128-byte) Object-type transfers.
  10. Key in the PC File Name -- this is what you will call the downloaded member on the C: drive of the Elixir workstation PC, and use as the input name to the Elixir so you should name the file with Xerox naming conventions.

    Example: A laser form source member would have a suffix of .FSL (i.e., uvats1.fsl)

  11. Identify the disk drive/path on the Elixir workstation for the target of the transfer.

    C:\aaelixtm has been created for this, but you may optionally choose to create your own temporary directory.

  12. Click OK when ready.

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.