•       IBM 3835 Central Printer

The North system 3835 printer is not moving to Titan. Instead, jobs that would print on this printer (by specifying BURST=Y or FORMS=x290) will be directed to the 3160 cut-sheet printer—if you have a North JOB statement.

This switch should be transparent—the output produced by the 3160 should be identical to that produced by the 3835. However, if you use a special formdef or pagedef, you may need to have these definitions installed on Titan. Contact TASC at (301) 594-6248, and ask to speak to a Titan consultant.

 •        BOX Numbers

All Titan USERids propagated from the North system have a default output box number prefaced by a P (for Parklawn). If you run a batch job on Titan, the output will be routed to your Parklawn box number unless you specify otherwise. However, if you include a /*BOX statement in your JCL, you need to include the P, since the /*BOX will override any default box number.

 •       Increased Region Requirements

Because the Titan operating system is several version levels higher than the North system, some batch jobs are experiencing increased region requirements. If your job fails because of region, simply increase the region and rerun.

 •       USERid Length Implications

You need to consider applications that capture the RACFid. If your application is expecting to handle 3 characters, it may need to be modified to accept 3 or more characters. On Titan, USERids/RACFids/TSOids are interchangeable and variable in length—from 3 to 7 characters.

To ease migration, all North TSOids ($iii) were brought over to become the USERid/RACFid/TSOid on Titan. South system USERids propagated to Titan will be 7 characters in length. Once the North and South systems are completely migrated to Titan, USERids can be any unique alphanumeric character string from 3 to 7 characters in length.

 •       Tape Expiration

On Titan, you define the expiration date for tape data at the time you create it by coding an expiration date or retention period in your JCL. JCL that creates a new tape data set and does NOT include expiration information (EXPDT= or RETPD=) will FAIL.

Although most North system users code tape expiration dates, Titan requires tape expiration dates since the 5-day default does not exist.

 •       Tape Security

Unlike the North and South systems, tape data set security on Titan is handled by RACF permissions on a data-set rather than volume basis. The RACF generic profiles in place on Titan apply to both tape and disk data sets. Since option P.17 (TPERMIT) in ISPF—for protecting tapes on a volume basis—does not exist on Titan, users may need to modify their RACF profiles to provide the same level of access to tape data as they now have.

 •       JCL

To simplify the transition to Titan, CIT uses software to automatically recognize North and South system JOB statements and JES2 /* statements, and convert them to execute the jobs in the appropriate Titan job class and at the appropriate time.

If you change your North or South JOB statement however, you will need to change your JES2 /* statements as well as any statements that direct output to the 3835 printer to conform to Titan format since they will no longer be recognized properly. (See section above on the 3835 central printer.)