August 19, 2003

Series on South Migration

CIT plans to shut down the South system effective January 12, 2004. Watch two Web sites regularly—Titan/South System News and the Titan Transition. Both Web pages are continually updated.

This is the fifth article in the series on the migration processs—so that you don't miss important news and you do have a smooth transition to Titan. These articles are reprinted from Titan Transition Migration Process Web page.

Topics to be covered in this series over the next months

1.   Determine your USERid(s) and password    
2.   Logon to Titan (TSO)—Changes
3.   Review your data security needs
4.   Access NIH Wylbur
5.   Test your batch jobs     [TitanPrep] [JCL changes]    < ARTICLE BELOW
6.   Review your tapes with the Web Tape facility     [moving tapes] [tape JCL]

5. Test Your Batch Jobs

•     Locate your JCL
•     Use the TitanPrep tool to determine how you will need to change your JCL.
•     A quick overview of JCL changes

•     Locate your JCL.

•     TitanPrep—A New Tool to Get Your JCL Ready for Titan

TitanPrep is a new WYLBUR Enter command that scans your South system JCL and shows you the changes that may be needed to run it on Titan.  To use this new tool, log on to WYLBUR and type:

ENTER TITANPREP

You will be prompted for the name of the data set that contains your JCL.  If you enter the name of a partitioned data set (PDS), TITANPREP will analyze each member.  For each data set (or member) being scanned, an output data set is created that contains an analysis of the JCL you submitted.  The naming convention for these output data sets is aaaaiii.TITAN.PREP.Dyyddd.Thhmmss.

Each output dataset will consist of one, two or three parts.

• Part one contains messages from scanning the JCL.
• Part two appears only if SAS code is scanned.  It flags any SAS statement that dynamically allocates a dataset owned by another user.
• Part three lists the expanded JCL, with statement numbers.  These numbers are referenced in the first part.

  Example:

  The following example shows messages from part one of the output data set:

  ************** Analysis of Dataset iii.HHS.DISKMAP **************
  
  The Job (iiiDISKM) runs under the Account: aaaa and Initials: iii.
  
  *WARNING* Statement 4 is a /*TITLE statement which is not supported on Titan and will be ignored.
  
  *ERROR* In statement 14 "PGM=DISKMAP" is not supported on Titan.
  Code "// EXEC DISKMAP" for DISKMAP on Titan.
  
  *WARNING* In statement 19 / Step Name (STEP1) another user's dataset (bbbbjjj.ESC.PRODUCTN.LOAD) is referenced.
  RACF authorization is needed.
  
  *****************************************************************

Each message is marked to indicate the message type:

• *WARNING* -- warns of a possible error.  You may need to make a change.

  Warning messages include statements that are not supported on Titan but will not cause an error because they are ignored. For clarity, you may want to clean up your JCL after you move to Titan.

  Warning messages are also issued if you access any data sets under a different account/initials (userid).  You will need to ensure that you have the proper RACF permission to these data sets.

  • Reading a data set requires READ access.
  • Writing to a data set requires UPDATE access.
  • Creating or deleting a data set requires ALTER access.

  Check your RACF access to data sets via Titan Web RACF by selecting If a data set is protected and if you have access, in the RACF Profiles Display section. If you do not know who owns the data set, go to the South System Customer Locator and enter the owner initials to see the name and contact information.

• *ERROR* -- a definite problem.  This JCL will not work on Titan.

  You must modify your JCL before you can run it on Titan.  For example, you may be executing a procedure that does not exist on Titan or writing to a tape and need to include expiration information for the tape.

For questions on using TitanPrep, call TASC at 301-594-6248. For information about Titan JCL and utilities, see the Titan Batch Processing manual.

The ENTER TITANPREP tool makes it easier for you to determine what is needed to make your JCL "Titan-ready", but it is not infallible.  The final test of your JCL is to run it on Titan.

1. JOB STATEMENTS:
   • Your South JOB statements continue to work on Titan.
   • South JOB classes automatically translate to Titan JOB classes (X or L).
   • On Titan job statements, jobnames do not need to begin with your Titan USERid.
   • If you code USER=iii on your JOB statement you need to change it to USER=aaaaiii on Titan - you can make this change on the South without causing any problems.
2. TAPE JCL:
   • For new tape data sets you need to specify the expected expiration date of the data set at creation time, using the expiration date parameter (EXPDT=) or the retention period parameter (RETPD=). You can change this expiration date at a later time using the Tape inventory facility (option L.5 of ISPF).
   • /*MESSAGE cards are not needed on Titan but do not need to be removed - they are ignored on Titan.
   • Tape UNITnames:
     • The South system UNITname of TAPE works on Titan - no need to change your JCL.
     • The South system UNITname of CTAPE no longer refers to foreign/special tapes - on Titan it means the same as TAPE.
     • Foreign tape UNITnames on Titan are FRGN6250, FRGN3480 and FRGN3490.
   • If you cycle through a set of tapes, rewriting them on a regular basis, you may want to change your process.
3. PRINTING:
   • Box numbers do not change.
   • For forms other than STD you need to change your JCL to code FCB= (or FORMDEF=) and PAGEDEF= in addition to FORMS=. This change is for batch only - WYLBUR LIST OFF options do not change.
   • /*DDOUT and /*JOBOUT are not supported on Titan. Use the OUTPUT JCL statement instead.
4. DISK UNITNAMES:
   • All South system disk UNITnames are supported on Titan (FILE, TMP, MSS). There is no need to change your JCL.
   • Titan has two new UNITnames: DISK2YR (retained for 2 years after last use) and DISK7YR (retained for 7 years after last use).
5. JCL IGNORED:
   • Some South JCL doesn't work on Titan. It is ignored and doesn't cause your job to fail.
6. JCL TO CHANGE:
   • Some South JCL must be changed to run on Titan or your job will fail.
7. PROC/SOFTWARE CHANGES:
   • Most South programs and cataloged procedures are available on Titan. A few are not available.