Titan header and trailer pages look different from South system header and trailer pages.
VPS Firewall Configuration for Titan
Since Titan has a different ip address than the South system, VPS users will need to make changes to their firewall configurations. The new Titan ip address can be added to your firewall any time before you begin VPS printing there. Please refer to the Titan Printing page for information on how to make these changes.
Printing South Batch Jobs
To prepare for migration to Titan, South system users who route jobs to print on VPS or Remote printers may wish to move their printers to Titan and make the changes outlined below to permit their jobs executed on the South system to print on these Titan-attached printers. To do this you will need to change the destination JES2 nodename by adding a /*ROUTE PRINT NIHJES2.printername statement to your JCL. These statements can be left in your JCL after you move to Titan.
/*ROUTE PRINT NIHJES2.printername
NOTE: Be sure to use the term PRINT rather than OUTPUT in the above statement to ensure that this works correctly. The /*ROUTE PRINT and /*ROUTE OUTPUT do not function in quite the same way.
Printing from Wylbur on South
Use printername@NIHJES2 for the value of the PRINT option on CONDENSE, LIST RETRIEVE, RUN, SET BATCH and SET JOB commands.
To print a listing of the default active file:
list print NIHCxxxx@NIHJES2
To submit a job and have the output printed:
run print NIHCxxxx@NIHJES2
To specify the destination for an individual SYSOUT data set:
The DEST parameter on the DD statement for a SYSOUT data set does not support a two level name. In order to specify that a SYSOUT data set produced in a job submitted on South should print on a TITAN printer, it is necessary to use the OUTPUT JCL statement and the OUTPUT parameter on the SYSOUT DD statement.
Example:(job card) //outputname OUTPUT DEST=NIHJES2.NIHCxxxx . . (exec statement) . . //ddname DD SYSOUT,OUTPUT=*.outputname
Further information on the use of the OUTPUT JCL statement is available in the Titan Batch Processing manual.
Processing ISPF LIST, LOG and HARDCOPY output
You can use a two level destination value for local print or print via batch by including a /*ROUTE PRINT statement in the batch print jcl.
Local print of LIST output:Specify Disposition of List Data Set Command ===> List Data Set (ZZYZKL2.SPF0.LIST) Disposition: Process Option . . . 1. Print data set and delete 2. Delete data set without printing 3. Keep existing data set and continue with new data set SYSOUT class . . . . Local printer ID or writer-name . . . . . NIHJES2.NIHCxxxx Press ENTER key to process the list data set. Enter END command to exit without processing the list data set. Job statement information: (Required for system printer) . . . //* . . . //* . . . //* . . . //* F1=Help F2=Split F3=Exit F9=Swap F12=Cancel Batch print of LIST data set: Specify Disposition of List Data Set Command ===> List Data Set (ZZYZKL2.SPF0.LIST) Disposition: Process Option . . . 1. Print data set and delete 2. Delete data set without printing 3. Keep existing data set and continue with new data set SYSOUT class . . . . A Local printer ID or writer-name . . . . . Press ENTER key to process the list data set. Enter END command to exit without processing the list data set. Job statement information: (Required for system printer) . . . (job card) . . . /*ROUTE PRINT NIHJES2.NIHCxxxx . . . //* . . . //* F1=Help F2=Split F3=Exit F9=Swap F12=Cancel
Printing Jobs in OUTPUT HOLD using ISPF Option 3.8 (OUTLIST)
Currently ISPF Option 3.8 does not support the use of two level destination names in the OUTPUT DEST field. In order to print from South to a TITAN VPS printer, it is necessary to include a /*ROUTE PRINT NIHJES2.printername statement in the job before submitting it. If such a statement is included in the job, then specifying 'P' for the job will cause it to print from a TITAN printer. Alternatively, you can specify K for keep after fetching the job and then print the saved output. See examples above for processing LIST, LOG and HARDCOPY output.
Special Forms and Character Sets
In order to keep obsolete information out of Titan's image library, only those forms control buffer (FCB) images, universal character set (UCS) images, FORMDEFs, PAGEDEFs, and character sets (CHARS) that we know are still being used have been copied from the South System image library. Unfortunately, there is no foolproof way to determine every image library member in use.
While transitioning to Titan, it is possible that some users' jobs may not initially print (or get an error message) because a necessary print element has not yet been copied.
If your JCL specifies "FCB=", "UCS=", "FORMDEF=", PAGEDEF=", or "CHARS=", and you are using a form other than those documented in the Titan Batch Processing manual (e.g., 900 or 999, etc.), please verify that your job will print correctly on Titan. If it does not print, please call TASC and ask to speak to a Titan consultant.
RJE Job Submission and Remote Printing
If you use a remote job entry (RJE) workstation to submit jobs to the central facility, you must change the SIGNON control statement in order to communicate with Titan. The password stays the same.
The format of the SIGNON control statement for Titan is:
/*SIGNON NIHTTNRMTnnn passwordwhere nnn is the remote terminal workstation number and password is the password assigned by CIT.
NIHTTN must begin in column 10, RMTnnn in column 16, and password in column 73.
For More Information
For information on batch processing and job control language, refer to "Remote Job Submission" in the Titan Batch Processing manual.
Titan Specifics Summary page
NIH Computer Center| Comments | Accessibility
September 9, 2003