Dev Guide

ASIA PACIFIC PROCESSING CENTER
GCB DEVELOPERS’ GUIDE

Release 1.0
Octo ber 15, 1999
GLOBAL CONSUMER BANKING
COPYRIGHT NOTICE
Copyright  (1996) by Citibank N.A.
All rights reserved. This material is confidential and proprietary to CITIBANK, N.A. and no part of this
material should be reproduced, published in any form by any means, electronic or mechanical including
photocopy or any information storage or retrieval system nor should the material be disclosed to third
parties without the express written authorization of CITIBANK, N.A.
1
ASIA PACIFIC COMPUTERS CENTER DEVELOPER’S GUIDE
AMENDMENT RECORD
Change Control Date Section Change Description

No.
1 15 Oct 3.4 New Library Added
2 4.3.1 New Section Added For Job Names - Cards
3 4.4 Additional Data For Proc Naming Standards - Country
4 4.5 New Parmlib Member Naming Standards Added
5 Country Specific Parmlib Added
6 5.7.2 New Section Added - Close/Open CICS Online Files
7 5.7.6 New Section Added - Page for the Assigned Person When The
Critical Job Abend
8 5.8.10 New Section Added - PROCS Override
9 5.8.11 New Section Added - Variable List for Library
10 5.8.12 New Section Added - Include Member
11 5.8.13 New Section Added - Calling JCL, PROCS Statement
12 5.8.14 New Section Added - Qualifier
13 5.8.15 New Section Added - Reference
14 5.9.11 New Section Added - Manual JCL Override
15 10.2 New Application Codes Added
16 02-Apr-98 10.1 New Country Codes Added
17 10.2 New Application Codes Added
April 16, 1997 2

ASIA PACIFIC COMPUTER CENTRE DEVELOPER’S GUIDE
TABLE OF CONTENTS
1. INTRODUCTION.................................................................................................................................. 7
2. DISTRIBUTION.................................................................................................................................. 12
3. DATASET NAMING STANDARDS..................................................................................................... 13

3.1. TSO DATASETS.............................................................................................................................. 13
3.2. CARD / NON SYSTEMATICS SYSTEMS APPLICATION DATASETS...........................................................13
3.3. BANKING SYSTEMS (SYSTEMATICS) APPLICATION DATASETS.............................................................14
3.4. APPLICATION LIBRARIES.................................................................................................................. 15
4. JOB RELATED STANDARDS............................................................................................................ 17
4.1. JOB CLASS STANDARD(S)................................................................................................................ 17
4.2. JOB INITIATOR STANDARDS.............................................................................................................. 17
4.3. JOB NAMES.................................................................................................................................... 17
4.3.1. Job Names -- Cards............................................................................................................. 19
4.4. PROC NAMING STANDARDS............................................................................................................. 21
4.5. PARMLIB MEMBER NAMING STANDARDS........................................................................................... 22
4.6. USER PARAMETER NAMING STANDARDS......................................................................................... 23
5. OPERATIONS ACCEPTANCE STANDARDS....................................................................................24
5.1. FILE TRANSFER............................................................................................................................... 24
5.2. FILE CONTROL FOR BANK (SYSTEMATICS) APPLICATIONS..................................................................24
5.2.1. Checking For Data Integrity Of Files......................................................................................24
5.2.2. Checking for Duplicate Processing........................................................................................ 25
5.3. FILE CONTROL FOR CARDS (ECS) APPLICATIONS.............................................................................25
5.3.1. Checking for data integrity of files.......................................................................................... 26
5.3.2. Checking for duplicate processing......................................................................................... 26
5.3.3. Algorithm for Hash Total Computation...................................................................................27
5.4. ONLINE........................................................................................................................................... 27
5.5. BATCH............................................................................................................................................ 28
5.5.1. Application Design Consideration.......................................................................................... 28
5.5.2. Archival/Housekeeping.......................................................................................................... 28
5.6. AF/O PERATOR AUTOMATION............................................................................................................ 28
5.6.1. System Setup......................................................................................................................... 28
5.6.2. Traps & Execs........................................................................................................................ 29
5.6.3. Message Trapping & Automation........................................................................................... 29
5.7. CONSOLE MESSAGE NAMING CONVENTION......................................................................................29
5.7.1. External CICS Interface......................................................................................................... 29
5.7.1.1. Invoking EXCICLN1..............................................................................................................................30
5.7.1.2.Parameters for EXCICLN1.................................................................................................................... 30
5.7.1.3. Return Codes................................................................................................................................... 31
5.7.2. CLOSE/OPEN CICS ONLINE FILES....................................................................................31
5.7.3. Trigger CICS Transaction....................................................................................................... 31
5.7.4. Submit Batch Job................................................................................................................... 32
5.7.5. XCOM File Transfer............................................................................................................... 32
5.7.6. Page For The Assigned Person When The Critical Job Abend...........................................33
5.7.7. Monitor LU............................................................................................................................. 33
5.7.8. Start OASM Transaction........................................................................................................ 34
5.7.9. Issue Operator Commands.................................................................................................... 34
5.7.10.Startup CICS............................................................................................................................ 34
5.7.11. Shutdown CICS....................................................................................................................... 35
5.7.12.File Transfer Automation.......................................................................................................... 35
5.7.13.Load NCP................................................................................................................................ 36
5.8. JCL STANDARDS............................................................................................................................. 36
5.8.1. Jobs....................................................................................................................................... 36
October 15, 1997 3

5.8.2. Jobcard.................................................................................................................................. 36
5.8.3. Parm Field.............................................................................................................................. 36
5.8.4. Catalogued Datasets.............................................................................................................. 36
5.8.5. Sort Work Files...................................................................................................................... 37
5.8.6. Operator Replies.................................................................................................................... 37
5.8.7. Definition of the External File Interface..................................................................................37
5.8.8. External System Interfaces.................................................................................................... 37
5.8.9. Temporary Files..................................................................................................................... 37
5.8.10.PROCS Override..................................................................................................................... 37
5.8.11.Variable List for Library............................................................................................................. 38
5.8.12.Include Member....................................................................................................................... 38
5.8.13.Calling JCL, PROCS Statement.............................................................................................. 38
5.8.14.Qualifier.................................................................................................................................... 38
5.8.15.Reference................................................................................................................................ 38
5.9. RERUN........................................................................................................................................... 38
5.9.1. Restart Overview................................................................................................................... 38
5.9.1.1.Manual JCL Override.............................................................................................................................39
5.9.2. OPC - Batch Auto Recovery.................................................................................................. 41
5.9.2.1.OPC - Catalog Management................................................................................................................. 43
5.10. PROCEDURE LIBRARY SPECIFICATIONS......................................................................................... 44
5.10.1.Procedure Format.................................................................................................................... 44
5.10.2.The Proc Description Segment................................................................................................ 44
5.10.3.The Proc Statement Segment................................................................................................. 44
5.11. THE STEP DESCRIPTION SEGMENT............................................................................................... 45
5.11.1.The STEP JCL Statements...................................................................................................... 45
5.11.2.The EXEC Statement............................................................................................................... 46
5.12. TAPE MANAGEMENT STANDARDS.................................................................................................. 46
5.12.1.Tape Retention Standard......................................................................................................... 46
5.13. BACKUP/RESTORES..................................................................................................................... 46
5.14. THE DD STATEMENTS.................................................................................................................. 47
5.15. APPLICATION DOCUMENTATION..................................................................................................... 48
5.15.1.Application Overview............................................................................................................... 49
5.15.2.System/Application Flow Chart................................................................................................ 49
5.15.3.On Call Procedures.................................................................................................................. 49
5.15.4.Data Center Operations Job Documentation...........................................................................49
5.15.5. Report Distribution (Control-D Requirements)........................................................................50
5.16. OUTPUT STANDARDS................................................................................................................... 51
5.16.1. Output................................................................................................................................. 51
5.16.2.Sysout Statements................................................................................................................... 51
5.16.3. Parameter Description........................................................................................................ 52
5.16.4.Remote Printing Limits............................................................................................................. 52
5.16.5.Standard Operations Utilities................................................................................................... 52
5.16.6.Sysout Deletion........................................................................................................................ 52
6. CICS ENVIRONMENTS..................................................................................................................... 53
6.1. TEST CICS REGION CHANGES........................................................................................................ 53
6.1.1. Implementation Requirement................................................................................................. 53
6.1.2. Process.................................................................................................................................. 53
6.1.2.1.Naming Conventions............................................................................................................................. 54
6.1.2.2.New Groups To Be Added To The List...................................................................................................55
6.1.2.3.Training, UAT And PRODUCTION Changes.........................................................................................56
6.2. APCC CICS CHANGE PROCEDURE................................................................................................. 56
6.2.1. STDC.MDC.CICS.MODELS.................................................................................................. 56
6.2.2. SADC.MCM.JCL.CUAT.BASE0............................................................................................. 56
6.2.3. SADC.MCM.JCL.CPRD.BASE0............................................................................................ 56
6.2.4. STDC.MDC.CICS.UAT.REQUEST.DONE.............................................................................56
6.2.5. STDC.MDC.CICS.PROD.REQUEST.DONE..........................................................................56
6.2.6. Training, UAT & Production.................................................................................................... 56
October 15, 1997 4

6.2.7. Emergency Update Procedure............................................................................................... 58

6.3. CICS DEFAULT USERS.................................................................................................................... 58
6.3.1. Cardpac Application Regions................................................................................................. 58
6.3.2. Systematic Application Regions............................................................................................. 58
6.4. CICS PRESET USERID(S)................................................................................................................ 59
6.4.1. Cardpac and Banking Application Regions............................................................................59
6.5. CICS SOURCE, COPY BOOKS, LOADLIBS AND CHANGEMAN PACKAGES.............................................60
6.6. CICS STARTUP DECK (JCL) FOR ALL CICS VERSION AND CHANGEMAN PACKAGES..........................60
6.7. CICS SOURCE, LOADLIBS AND CHANGEMAN PACKAGES..................................................................60
6.8. CICS NAMING CONVENTION............................................................................................................ 61
6.8.1. Country Base CICS Regions.................................................................................................. 61
6.8.2. TOR Country Base CICS Regions......................................................................................... 62
6.8.3. TOR Common Cards CICS Regions......................................................................................62
6.8.5. Migration / Conversion of Cards Applications.........................................................................63
6.8.5.1.Dataset Naming Convention for the CONV / PRODUCTION CICS......................................................63
6.9. MIGRATION / CONVERSION OF BANKING APPLICATIONS.....................................................................63
6.9.1. Dataset Naming Convention for the CONV/PRODUCTION CICS.........................................63
6.10. CICS VERSION 3.3 RESOURCE DEFINITION ON-LINE (RDO).........................................................64
6.10.1. To Apply Changes For RDO............................................................................................... 64
6.10.2. RDO Definitions & Jobs - Sample Skeleton........................................................................64
6.10.3.STDC.MCI.SRC.RDO.............................................................................................................. 65
6.10.4.STDC.MCI.SRC.RDO ($INDEX).............................................................................................. 66
6.10.5.STDC.MCI.SRC.RDO ($LSTNAME)........................................................................................ 67
6.10.6. STDC.MCI.SRC.RDO ($GRPNAME).................................................................................67
6.10.7. STDC.MCI.SRC.RDO (DFHCSDUP)..................................................................................68
6.10.8. STDC.MCI.SRC.RDO (RDADVISA)...................................................................................68
6.10.9. STDC.MCI.SRC.RDO (TLU2VISA)......................................................................................... 69
6.10.10.STDC.MCI.SRC.RDO (TLU2000N).......................................................................................70
6.10.11.STDC.MCI.SRC.RDO (CSDLIST).......................................................................................... 71
6.10.12.TEST, SIT, UAT CICS Regions in ‘g’ RND LPAR (Telepark)..............................................71
6.10.12.1. ICBS Group................................................................................................................................... 71
6.10.12.2.RCC Group........................................................................................................................................ 72
6.10.13.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)..............................................72
6.10.13.1.RCC & PBG Group............................................................................................................................ 72
6.10.14.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)..............................................73
6.10.14.1.RCC & PBG Group............................................................................................................................ 73
6.10.15.Production CICS Regions in PROD LPAR.............................................................................73
6.10.16.Test CICS Regions in HONG KONG RND LPAR (CINTECH II)...........................................73
6.10.17.QA CICS in QA LPAR............................................................................................................ 74
6.10.18.Production Regions in Hong Kong LPAR...............................................................................74
6.10.19.On-Line Only On User Request............................................................................................. 74
6.10.20.Test and UAT CICS Regions in Australia RND LPAR............................................................74
6.10.21.Production CICS Regions in AUSTRALIA Production LPAR..................................................74
6.10.22.Update SNT Table in Test, UAT and Production HKG CICS..................................................74
6.10.23.CICS Suffixes......................................................................................................................... 76
6.10.23.1. TEST for Version 2.1.2 and Version 3.3.0....................................................................................76
6.10.23.2.TEST for Version 4.1.0....................................................................................................................... 77
6.10.23.3.UAT for Version 1,2,3 and 4...............................................................................................................78
6.10.23.4.PRODUCTION for Version 1,2,3, and 4............................................................................................79
6.11.DFHRPL LIBRARY CONCATENATION STANDARDS...............................................................................80
6.11.1.RND - DFHRPL Library Concatenation Standards...................................................................80
6.11.1.1.AOR Region......................................................................................................................................... 80
6.11.1.2.TOR Region.......................................................................................................................................... 80
6.11.2.Pre-UAT and UAT- DFHRPL Library Concatenation Standards...............................................81
6.11.2.1.AOR Region......................................................................................................................................... 81
6.11.2.2.TOR Region.......................................................................................................................................... 81
6.11.3.Training - DFHRPL LIBRARY CONCATENATION Standards..................................................82
6.11.3.1.AOR Region......................................................................................................................................... 82
6.11.3.2.TOR Region.......................................................................................................................................... 82
6.11.4.Conversion - DFHRPL Library Concatenation Standards........................................................83
October 15, 1997 5

6.11.4.1.AOR Region......................................................................................................................................... 83
6.11.5. PROD - DFHRPL Library Concatenation Standards...........................................................83
6.11.5.1.AOR Region......................................................................................................................................... 83
6.11.5.2.TOR Region.......................................................................................................................................... 84
7. PROGRAMMING LANGUAGE STANDARDS...................................................................................85
7.1. COBOL.................................................................................................................................... 85
7.2. ASSEMBLER........................................................................................................................... 85
7.3. NATURAL................................................................................................................................. 85
7.4. UTILITIES LANGUAGE............................................................................................................ 85
8. GUIDELINES FOR CHANGEMAN SET-UP.......................................................................................86
8.1. PRE-SETUP MEETING..................................................................................................................... 86
8.2. PROJECT MANAGERS TO INCLUDE CHANGEMAN COMPILATION TIME IN PROJECT PLANNING..........86
8.3. APPLICATION PROJECT-ID STANDARD.............................................................................................. 86
8.4. SIT PROMOTION LIBRARIES............................................................................................................. 86
8.5. UAT PROMOTION LIBRARIES............................................................................................................ 87
8.6. BASELINE LIBRARIES....................................................................................................................... 87
8.7. APPROVAL OF PACKAGES................................................................................................................ 88
9. STORAGE MANAGEMENT GUIDELINES........................................................................................ 89
9.1. INTRODUCTION............................................................................................................................... 89
9.2. SMS CLASSES AND GROUPS.......................................................................................................... 89
9.3. HOUSE-KEEPING RULES.................................................................................................................. 89
9.4. DFHSM MIGRATION POLICY........................................................................................................... 90
9.4.1. DFHSM MIGRATION POLICY FOR APCC PRODUCTION LPAR........................................90
9.4.2. DFHSM MIGRATION POLICY FOR APCC RND/UAT LPAR.................................................90
9.5. SRS/ACC................................................................................................................................. 91
10. APPENDICES.................................................................................................................................. 93
10.1. APPENDIX A - COUNTRY CODES................................................................................................. 93
10.2. APPENDIX B - APPLICATION CODES.............................................................................................. 94
10.3. APPENDIX C - STANDARD REPORT FORMAT -- NON-SYSTEMATICS.................................................97
10.4. APPENDIX D - STANDARD REPORT FORMAT - SYSTEMATICS...........................................................98
10.5. APPENDIX E - SAMPLE LAYOUT OF HEADER AND TRAILER RECORDS IN INTERFACE FILES...............99
10.6. APPENDIX F - DATA CENTER OPERATION JOB DOCUMENTATION...................................................100
10.7. APPENDIX G - REPORT DISTRIBUTION......................................................................................... 101
10.8. APPENDIX H - PRODUCTION JOB MODIFICATION REQUEST FORM.................................................102
10.9. APPENDIX I - RACF PROFILE APPLICATION.................................................................................104
10.10. APPENDIX J - APCC SLA DEVELOPMENT W ORK........................................................................108
10.11.APPENDIX K - FORMAT FOR INTERFACE FILE HEADER AND TRAILER RECORDS.................................109
October 15, 1997 6

October 15, 1997 7

1. INTRODUCTION
This document provides a reference for all development and data center staff. It shows the standards and
guidelines on the IBM Mainframe Environment for the Global Consumer Bank and provides an insight on the
process and procedures associated with implementing or changing application systems.
Several templates have been imbedded within the document to be used when providing information to the Asia
Pacific Processing Center (APPC).
The document provides a framework that must be adhered to when developing and maintaining systems.
To ensure compliance, enforcement is necessary. All new systems and major modifications to existing systems
must comply with the standards in this guide before they are accepted for production. It is important that staff do
not violate the standards even when they find it cumbersome. Besides enforcement, we need to provide
channels for improvements and revisions of standards. This is important to keep the document ‘alive’ and ‘current’.
All correspondence in relation to this document is to be sent to the relevant section owners as detailed
below. Via OpenMail.
1. INTRODUCTION...................................................................................................................... LEONG SP
2. DISTRIBUTION........................................................................................................................ LEONG SP
3. DATASET NAMING STANDARDS.........................................................................................................

3.1. TSO DATASETS............................................................................................................... JAMES BERTI
3.2. CARD / NON SYSTEMATICS SYSTEMS APPLICATION DATASETS.......................................... JEFFREY GOH
3.3. BANKING SYSTEMS (SYSTEMATICS) APPLICATION DATASETS............................................. JEFFREY GOH
3.4. APPLICATION LIBRARIES.................................................................................................. JEFFREY GOH
4. JOB RELATED STANDARDS................................................................................................................
4.1. JOB CLASS STANDARD(S)................................................................................................. JAMES BERTI
4.2. JOB INITIATOR STANDARDS............................................................................................... JAMES BERTI
4.3. JOB NAMES.................................................................................................................... JEFFREY GOH
4.3.1. Job Names -- Cards.............................................................................................. JEFFREY GOH
4.4. PROC NAMING STANDARDS............................................................................................. JEFFREY GOH
4.5. PARMLIB MEMBER NAMING STANDARDS........................................................................... JEFFREY GOH
4.6. USER PARAMETER NAMING STANDARDS......................................................................... JEFFREY GOH
5. OPERATIONS ACCEPTANCE STANDARDS........................................................................................
5.1. FILE TRANSFER............................................................................................................ MUSTAFA SIDEK
5.2. FILE CONTROL FOR BANK (SYSTEMATICS) APPLICATIONS............................................... MUSTAFA SIDEK
5.2.1. Checking For Data Integrity Of Files................................................................... MUSTAFA SIDEK
5.2.2. Checking for Duplicate Processing...................................................................... MUSTAFA SIDEK
5.3. FILE CONTROL FOR CARDS (ECS) APPLICATIONS.......................................................... MUSTAFA SIDEK
5.3.1. Checking for data integrity of files....................................................................... MUSTAFA SIDEK
5.3.2. Checking for duplicate processing....................................................................... MUSTAFA SIDEK
5.3.3. Algorithm for Hash Total Computation................................................................. MUSTAFA SIDEK
5.4. ONLINE........................................................................................................................ MUSTAFA SIDEK
October 15, 1997 8

5.5. BATCH......................................................................................................................... MUSTAFA SIDEK

5.5.1. Application Design Consideration........................................................................ MUSTAFA SIDEK
5.5.2. Archival/Housekeeping........................................................................................ MUSTAFA SIDEK
5.6. AF/O PERATOR AUTOMATION.................................................................................. CHEE MIANG CHOON
5.6.1. System Setup............................................................................................... CHEE MIANG CHOON
5.6.2. Traps & Execs............................................................................................... CHEE MIANG CHOON
5.6.3. Message Trapping & Automation.................................................................. CHEE MIANG CHOON
5.7. CONSOLE MESSAGE NAMING CONVENTION............................................................. CHEE MIANG CHOON
5.7.1. External CICS Interface................................................................................ CHEE MIANG CHOON
5.7.1.1. Invoking EXCICLN1................................................................................................. CHEE MIANG CHOON
5.7.1.2.Parameters for EXCICLN1........................................................................................ CHEE MIANG CHOON
5.7.1.3. Return Codes....................................................................................................... CHEE MIANG CHOON
5.7.2. CLOSE/OPEN CICS ONLINE FILES.......................................................... CHEE MIANG CHOON
5.7.3. Trigger CICS Transaction.............................................................................. CHEE MIANG CHOON
5.7.4. Submit Batch Job.......................................................................................... CHEE MIANG CHOON
5.7.5. XCOM File Transfer...................................................................................... CHEE MIANG CHOON
5.7.6. Page For The Assigned Person When The Critical Job Abend..................CHEE MIANG CHOON
5.7.7. Monitor LU.................................................................................................... CHEE MIANG CHOON
5.7.8. Start OASM Transaction............................................................................... CHEE MIANG CHOON
5.7.9. Issue Operator Commands........................................................................... CHEE MIANG CHOON
5.7.10.Startup CICS................................................................................................... CHEE MIANG CHOON
5.7.11. Shutdown CICS.............................................................................................. CHEE MIANG CHOON
5.7.12.File Transfer Automation................................................................................. CHEE MIANG CHOON
5.7.13.Load NCP....................................................................................................... CHEE MIANG CHOON
5.8. JCL STANDARDS............................................................................................................. JEFFREY GOH
5.8.1. Jobs........................................................................................................................ JEFFREY GOH
5.8.2. Jobcard................................................................................................................... JEFFREY GOH
5.8.3. Parm Field.............................................................................................................. JEFFREY GOH
5.8.4. Catalogued Datasets.............................................................................................. JEFFREY GOH
5.8.5. Sort Work Files....................................................................................................... JEFFREY GOH
5.8.6. Operator Replies.................................................................................................... JEFFREY GOH
5.8.7. Definition of the External File Interface.................................................................. JEFFREY GOH
5.8.8. External System Interfaces.................................................................................... JEFFREY GOH
5.8.9. Temporary Files...................................................................................................... JEFFREY GOH
5.8.10.PROCS Override...................................................................................................... JEFFREY GOH
5.8.11.Variable List for Library............................................................................................. JEFFREY GOH
5.8.12.Include Member........................................................................................................ JEFFREY GOH
5.8.13.Calling JCL, PROCS Statement............................................................................... JEFFREY GOH
5.8.14.Qualifier.................................................................................................................... JEFFREY GOH
5.8.15.Reference................................................................................................................. JEFFREY GOH
5.9. RERUN........................................................................................................................... JEFFREY GOH
5.9.1. Restart Overview.................................................................................................... JEFFREY GOH
5.9.1.1.Manual JCL Override........................................................................................................... JEFFREY GOH
5.9.2. OPC - Batch Auto Recovery................................................................................... JEFFREY GOH
5.9.2.1.OPC - Catalog Management............................................................................................... JEFFREY GOH
5.10. PROCEDURE LIBRARY SPECIFICATIONS.......................................................................... JEFFREY GOH
5.10.1.Procedure Format.................................................................................................... JEFFREY GOH
5.10.2.The Proc Description Segment................................................................................. JEFFREY GOH
5.10.3.The Proc Statement Segment.................................................................................. JEFFREY GOH
5.11. THE STEP DESCRIPTION SEGMENT............................................................................... JEFFREY GOH
5.11.1.The STEP JCL Statements....................................................................................... JEFFREY GOH
5.11.2.The EXEC Statement............................................................................................... JEFFREY GOH
5.12. TAPE MANAGEMENT STANDARDS.................................................................................. JEFFREY GOH
5.12.1.Tape Retention Standard.......................................................................................... JEFFREY GOH
5.13. BACKUP/RESTORES...................................................................................................... JEFFREY GOH
5.14. THE DD STATEMENTS.................................................................................................. JEFFREY GOH
5.15. APPLICATION DOCUMENTATION..................................................................................... JEFFREY GOH
5.15.1.Application Overview................................................................................................ JEFFREY GOH
October 15, 1997 9

5.15.2.System/Application Flow Chart................................................................................ JEFFREY GOH

5.15.3.On Call Procedures.................................................................................................. JEFFREY GOH
5.15.4.Data Center Operations Job Documentation............................................................ JEFFREY GOH
5.15.5. Report Distribution (Control-D Requirements)......................................................... JEFFREY GOH
5.16. OUTPUT STANDARDS................................................................................................... JEFFREY GOH
5.16.1. Output.................................................................................................................. JEFFREY GOH
5.16.2.Sysout Statements................................................................................................... JEFFREY GOH
5.16.3. Parameter Description......................................................................................... JEFFREY GOH
5.16.4.Remote Printing Limits............................................................................................. JEFFREY GOH
5.16.5.Standard Operations Utilities.................................................................................... JEFFREY GOH
5.16.6.Sysout Deletion........................................................................................................ JEFFREY GOH
6. CICS ENVIRONMENTS.........................................................................................................................
6.1. TEST CICS REGION CHANGES................................................................................................... IAN LE
6.1.1. Implementation Requirement............................................................................................ IAN LE
6.1.2. Process.............................................................................................................................. IAN LE
6.1.2.1.Naming Conventions........................................................................................................................ IAN LE
6.1.2.2.New Groups To Be Added To The List............................................................................................. IAN LE
6.1.2.3.Training, UAT And PRODUCTION Changes................................................................................... IAN LE
6.2. APCC CICS CHANGE PROCEDURE............................................................................................ IAN LE
6.2.1. STDC.MDC.CICS.MODELS.............................................................................................. IAN LE
6.2.2. SADC.MCM.JCL.CUAT.BASE0......................................................................................... IAN LE
6.2.3. SADC.MCM.JCL.CPRD.BASE0........................................................................................ IAN LE
6.2.4. STDC.MDC.CICS.UAT.REQUEST.DONE......................................................................... IAN LE
6.2.5. STDC.MDC.CICS.PROD.REQUEST.DONE..................................................................... IAN LE
6.2.6. Training, UAT & Production............................................................................................... IAN LE
6.2.7. Emergency Update Procedure.......................................................................................... IAN LE
6.3. CICS DEFAULT USERS............................................................................................................... IAN LE
6.3.1. Cardpac Application Regions............................................................................................ IAN LE
6.3.2. Systematic Application Regions........................................................................................ IAN LE
6.4. CICS PRESET USERID(S)........................................................................................................... IAN LE
6.4.1. Cardpac and Banking Application Regions....................................................................... IAN LE
6.4.2. Regional Base Application Regions.................................................................................. IAN LE
6.5. CICS SOURCE, COPY BOOKS, LOADLIBS AND CHANGEMAN PACKAGES........................................ IAN LE
6.6. CICS STARTUP DECK (JCL) FOR ALL CICS VERSION AND CHANGEMAN PACKAGES.................... IAN LE
6.7. CICS SOURCE, LOADLIBS AND CHANGEMAN PACKAGES............................................................. IAN LE
6.8. CICS NAMING CONVENTION....................................................................................................... IAN LE
6.8.1. Country Base CICS Regions............................................................................................. IAN LE
6.8.2. Regional Base CICS Regions........................................................................................... IAN LE
6.8.3. TOR Country Base CICS Regions..................................................................................... IAN LE
6.8.4. TOR Common Cards CICS Regions................................................................................. IAN LE
6.8.5. Migration / Conversion of Cards Applications................................................................... IAN LE
6.8.5.1.Dataset Naming Convention for the CONV / PRODUCTION CICS................................................ IAN LE
6.9. MIGRATION / CONVERSION OF BANKING APPLICATIONS................................................................ IAN LE
6.9.1. Dataset Naming Convention for the CONV/PRODUCTION CICS.................................... IAN LE
6.10. CICS VERSION 3.3 RESOURCE DEFINITION ON-LINE (RDO)..................................................... IAN LE
6.10.1. To Apply Changes For RDO........................................................................................... IAN LE
6.10.2. RDO Definitions & Jobs - Sample Skeleton................................................................... IAN LE
6.10.3.STDC.MCI.SRC.RDO......................................................................................................... IAN LE
6.10.4.STDC.MCI.SRC.RDO ($INDEX)......................................................................................... IAN LE
6.10.5.STDC.MCI.SRC.RDO ($LSTNAME)................................................................................... IAN LE
6.10.6. STDC.MCI.SRC.RDO ($GRPNAME)............................................................................. IAN LE
6.10.7. STDC.MCI.SRC.RDO (DFHCSDUP)............................................................................. IAN LE
6.10.8. STDC.MCI.SRC.RDO (RDADVISA).............................................................................. IAN LE
6.10.9. STDC.MCI.SRC.RDO (TLU2VISA).................................................................................... IAN LE
6.10.10.STDC.MCI.SRC.RDO (TLU2000N)................................................................................... IAN LE
6.10.11.STDC.MCI.SRC.RDO (CSDLIST)..................................................................................... IAN LE
6.10.12.TEST, SIT, UAT CICS Regions in ‘g’ RND LPAR (Telepark).......................................... IAN LE
October 15, 1997 10

6.10.12.1. ICBS Group............................................................................................................................. IAN LE

6.10.12.2.RCC Group.................................................................................................................................. IAN LE
6.10.13.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)......................................... IAN LE
6.10.13.1.RCC & PBG Group...................................................................................................................... IAN LE
6.10.14.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)......................................... IAN LE
6.10.14.1.RCC & PBG Group...................................................................................................................... IAN LE
6.10.15.Production CICS Regions in PROD LPAR........................................................................ IAN LE
6.10.16.Test CICS Regions in HONG KONG RND LPAR (CINTECH II)....................................... IAN LE
6.10.17.QA CICS in QA LPAR........................................................................................................ IAN LE
6.10.18.Production Regions in Hong Kong LPAR.......................................................................... IAN LE
6.10.19.On-Line Only On User Request........................................................................................ IAN LE
6.10.20.Test and UAT CICS Regions in Australia RND LPAR........................................................ IAN LE
6.10.21.Production CICS Regions in AUSTRALIA Production LPAR............................................. IAN LE
6.10.22.Update SNT Table in Test, UAT and Production HKG CICS.............................................. IAN LE
6.10.23.CICS Suffixes.................................................................................................................... IAN LE
6.10.23.1. TEST for Version 2.1.2 and Version 3.3.0.............................................................................. IAN LE
6.10.23.2.TEST for Version 4.1.0................................................................................................................. IAN LE
6.10.23.3.UAT for Version 1,2,3 and 4......................................................................................................... IAN LE
6.10.23.4.PRODUCTION for Version 1,2,3, and 4...................................................................................... IAN LE
6.11.DFHRPL LIBRARY CONCATENATION STANDARDS.......................................................................... IAN LE
6.11.1.RND - DFHRPL Library Concatenation Standards.............................................................. IAN LE
6.11.1.1.AOR Region................................................................................................................................... IAN LE
6.11.1.2.TOR Region.................................................................................................................................... IAN LE
6.11.2.Pre-UAT and UAT- DFHRPL Library Concatenation Standards........................................... IAN LE
6.11.2.1.AOR Region................................................................................................................................... IAN LE
6.11.2.2.TOR Region.................................................................................................................................... IAN LE
6.11.3.Training - DFHRPL LIBRARY CONCATENATION Standards............................................. IAN LE
6.11.3.1.AOR Region................................................................................................................................... IAN LE
6.11.3.2.TOR Region.................................................................................................................................... IAN LE
6.11.4.Conversion - DFHRPL Library Concatenation Standards.................................................... IAN LE
6.11.4.1.AOR Region................................................................................................................................... IAN LE
6.11.5. PROD - DFHRPL Library Concatenation Standards...................................................... IAN LE
6.11.5.1.AOR Region................................................................................................................................... IAN LE
6.11.5.2.TOR Region.................................................................................................................................... IAN LE
7. PROGRAMMING LANGUAGE STANDARDS......................................................................................
7.1. COBOL......................................................................................... LEONG SOON PENG / JAMES BERTI
7.2. ASSEMBLER................................................................................ LEONG SOON PENG / JAMES BERTI
7.3. NATURAL..................................................................................... LEONG SOON PENG / JAMES BERTI
7.4. UTILITIES LANGUAGE................................................................. LEONG SOON PENG / JAMES BERTI
8. GUIDELINES FOR CHANGEMAN SET-UP...........................................................................................
8.1. PRE-SETUP MEETING....................................................................................................... JAMES BERTI
8.2. PROJECT MANAGERS TO INCLUDE CHANGEMAN COMPILATION TIME IN PROJECT PLANNING... .JAMES
BERTI
8.3. APPLICATION PROJECT-ID STANDARD............................................................................... JAMES BERTI
8.4. SIT PROMOTION LIBRARIES.............................................................................................. JAMES BERTI
8.5. UAT PROMOTION LIBRARIES............................................................................................. JAMES BERTI
8.6. BASELINE LIBRARIES......................................................................................................... JAMES BERTI
8.7. APPROVAL OF PACKAGES................................................................................................. JAMES BERTI
9. STORAGE MANAGEMENT GUIDELINES............................................................................................
9.1. INTRODUCTION................................................................................................................. JAMES BERTI
9.2. STORAGE GROUP............................................................................................................. JAMES BERTI
9.3. HOUSE-KEEPING RULES................................................................................................... JAMES BERTI
9.4. DFHSM MIGRATION POLICY............................................................................................. JAMES BERTI
9.4.1. DFHSM MIGRATION POLICY FOR APCC PRODUCTION LPAR.......................... JAMES BERTI
9.4.2. DFHSM MIGRATION POLICY FOR APCC RND/UAT LPAR................................... JAMES BERTI
10. APPENDICES......................................................................................................................................
October 15, 1997 11

10.1. APPENDIX A - COUNTRY CODES.................................................................................. JEFFREY GOH

10.2. APPENDIX B - APPLICATION CODES............................................................................... JEFFREY GOH
10.3. APPENDIX C - STANDARD REPORT FORMAT -- NON-SYSTEMATICS.................................. JEFFREY GOH
10.4. APPENDIX D - STANDARD REPORT FORMAT - SYSTEMATICS........................................... JEFFREY GOH
10.5. APPENDIX E - SAMPLE LAYOUT OF HEADER AND TRAILER RECORDS IN INTERFACE FILES......JEFFREY
GOH
10.6. APPENDIX F - DATA CENTER OPERATION JOB DOCUMENTATION..................................... JEFFREY GOH
10.7. APPENDIX G - REPORT DISTRIBUTION........................................................................... JEFFREY GOH
10.8. APPENDIX H - PRODUCTION JOB MODIFICATION REQUEST FORM................................... JEFFREY GOH
10.9. APPENDIX I - RACF PROFILE APPLICATION............................................................................ NED LIM
10.10. APPENDIX J - APCC SLA DEVELOPMENT W ORK……………………………………..… RAMON
KARINGAL
10.11.APPENDIX K - FORMAT FOR INTERFACE FILE HEADER AND TRAILER RECORDS................... JEFFREY GOH
October 15, 1997 12

2. DISTRIBUTION
Copies of the approved Standards document will be placed on the APPC Website.
October 15, 1997 13

3. DATASET NAMING STANDARDS

All dataset names should be qualified. Up to 10 qualifiers of from 1 to 8 characters each are allowed. The
maximum length for dataset names is 44 characters including the periods between qualifiers. The first level
qualifier is used to direct catalogue searches to a given user catalogue.
3.1. TSO Datasets
Programmers’ TSO private libraries always commence with their TSO user id and user assigned values in
the subsequent qualifiers:
tsouserid.xxxxx
Example:
RAABC.JCL.CNTL - private library containing JCL of TSO user RAABC.
3.2. Card / Non Systematics Systems Application Datasets

All dataset names must have more than one qualifier. The first and second qualifier of a data set name
helps in its identification. The first qualifier is a four-byte word and the second qualifier is three-bytes as
follows:
ABCC.NTT.xxxxxxxxx
where:
A Data Center Code (Singapore) as follows:
S - Asia Pacific Computer Center (Singapore)
B The nature of the dataset as follows:

T - Research & Development (R&D)
E - Education / Training (TRN)
A - User Acceptance Test (UAT)
P - Production
C - Conversion
CC Identifies the country code.

(Please refer to section on Appendix A for details).
N The type of dataset and can be either of the following:

B - Batch data
L - Online data
M - Mixed data
TT The type of application.

(Please refer to section on Appendix B for details).
xxxxxxxx 1 to 8 characters unique qualifier.
Example:
SPTH.LCP.CPCUS - the name of an online PROD CARDPAC file for Thailand
October 15, 1997 14

3.3. Banking Systems (Systematics) Application Datasets

ABCC.MID.GRP.DD.XX
where:
A data Center Code (Singapore) as follows:
B The nature of the data set as follows:

T - R&D
E - TRN
A - UAT
P - Production
C - Conversion

(Please refer to Appendix A for details).
MID is 5 characters in length

1st and 2nd characters represent the originating application
e.g. IM = IMPACS
The 3rd character is a ‘.’
4th and 5th characters represent the receiving application.
e.g. OL = Online
BC = Batch
XX = Application Code
GRP is 3 characters in length

It represents the country bank code
e.g. I07 = Philippines
DD is variable in length
It represents the file DD name
e.g. IMACTM = IMPACS account master file
XX is variable in length
Description of file attributes, use, etc. It is user-defined.
Standards: V* = VSAM file

BU = Batch file backup
S* = e.g. of sequential file and indicating what step it is created by.
Example:
1) STPH.IM.OL.I07.IMACTM.VSAM
e.g. R&D IMPACS online account master file, group one.
2) STPH.AM.FM.I07.AMFMF.SAM72
e.g. Cross application data transfer between AM & FM.
October 15, 1997 15

3.4. Application Libraries
Libraries must have the following naming conventions:
ABCC.MTT.XXX
where:
A Data Center Code (Singapore)
B The nature of the dataset:

T - R&D
E - TRN
A - UAT
P - Production
C - Conversion

M A constant indicating that the dataset is a library.

B - Batch Data
L - Online Data
M - Mixed Data
TT Identify the type of application.

(Please refer to section on Appendix B for details)
XXX A three-byte code identifying the contents of the library and can be any of
the following:
PRM System or Parameter library

MAC Macro library
CPY Copy books library
JCL JCL library
LOD Load module library - Online
MAP Map library
PRC Procedure library
SRC Source library
DAT Data library (R&D)
SDF Screen Definition Facility
MPS Map Copybook
SKE CICS Skeleton Program
TRB Total Relationship Banking
GRB Global Relationship Banking
DDM Data Definition Module
INS Insurance
DBB DB2 Bind Control
DBR DB2 DBRM
UPM User Parameter
Example:
STTH.MCP.SRC - Library containing DEVT. source codes for Thailand’s
CARDPAC system
October 15, 1997 16

The same CHANGEMAN procedure used for existing JCL will be used, i.e.
- Two level of approval (PC and APPLN)
- UAT JCL/PROCS/PARMlib/User PARMlib will be copied directly from RND to UAT. No

Changeman promote or demote is requred.
- JCL/PROCS/PARMlib/User PARMlib will be staged in Changeman baseline library for

production implementation. For JCL/PARMlib member, changes may be required for first
level qualifier but this will not be applicable to PROCS hence UAT PROCS member can
be used for baseline staging.
- SP will look into automation procedure which the first level qualifier can be auto changed
by system during staging.
Separate and new library will be created, the existing library/setup (e.g. Changeman setup etc.) will not be
changed until complete cutover and system is established.
* This will include the existing GB library, APPLN will re-stage members in the GB library
SP will advise on the impacts to this library name changes related to
- Changeman
- OPC/ESA setup
- RACF
- AF/Operator
- Backup etc.
ENV JCL PROCS PARMlib User PARMlib

RND STcc.Maa.JCL STcc.MAA.PRC STcc.Maa.PRM STcc.Maa.UPM
UAT SAcc.MGB.JCL SAcc.MGB.PRC Sacc.MG.PRM SAcc.MGB.UPM
UAT Base SAcc.MCM.JCL.ccGB. SAcc.MCM.PRC.ccGB. SAcc.MCM.PRM.ccGB SAcc.MCM.UPM.ccGB.
BASE0 Base0 .Base0 Base0
PROD SPcc.MGB.JCL SPcc.MGB.PRC SPcc.MGB.PRM SPcc.MGB.UPM
- Separate application library will be used in RND (by application)

- Common library in UAT and PRODUCTION
- cc = country ID
- aa = application ID Package
- pppp = Changeman Package ID which will be ccGB
ENV JCL PROCS PARMlib User PARMlib

RND STGB.Maa.JCL STGB.MAA.PRC STGB.Maa.PRM STGB.Maa.UPM
UAT SAGB.MGB.JCL SAGB.MGB.PRC SaGB.MG.PRM SAGB.MGB.UPM
UAT Base SAGB.MCM.JCL.ccGB SAGB.MCM.PRC.ccGB. SAGB.MCM.PRM.ccGB. SAGB.MCM.UPM.ccGB.
.BASE0 Base0 Base0 Base0
PROD SPGB.MGB.JCL SPGB.MGB.PRC SPGB.MGB.PRM SPGB.MGB.UPM
October 15, 1997 17

4. JOB RELATED STANDARDS

4.1. Job Class Standard(s)
The job class defines the priority and service a batch job obtains. It is imperative that the correct job
class is selected. This will ensure the system performs to its utmost capabilities. Measures have been put
in place to ensure stray jobs won’t have an adverse effect on the system.
The job Classes are as follows:-
CLASS DESCRIPTION
Y Jobs to run on the primary system with less than 2 seconds CPU time
W Jobs to run on the primary system with less than 10 seconds CPU time
U Jobs to run on the primary system
I Jobs to run on the secondary system
M Changeman submitted jobs
S System jobs to run on the primary system
C System jobs to run on the secondary system
A System jobs with subsystem dependencies, and to run, on the primary system
L Jobs to run on any system
4.2. Job Initiator Standards
The number of initiators set aside for batch jobs is 100. Primary systems will have all active initiators set
to classes SAYWU. Some initiators will be set to classes SAYWUL based on requirements for class L.
Secondary systems will have all active initiators set to CLI. Changeman will be given 3 initiators on the
system where the subsystem runs, and these initiators will be set to class M.
4.3. Job Names
An eight-byte name which identifies the job name:

ABB CCnnx
where:
A Identifies the nature of the job, i.e.:
T - R&D
S - SIT
A - UAT
P - Production
BB Country code.
CC Application code / software code.
(Please refer to section on Appendix B for details).
nn 00-9Z for standard job
A0-ZZ for country specific job
The rule is as long as the first position is numeric, it is a standard job. If the second position is
an alphabet, it is a country specific job. We will not use the alphabets O & I to avoid confusion.
x Frequency as below:
I = Initialize
D = Daily
W = Weekly
F = Fortnightly
M = Monthly
Q = Quarterly
October 15, 1997 18

H = Half yearly
Y = Yearly
A = Upon Request / Adhoc
T = One time jobs
B = Backup
R = Restore
October 15, 1997 19

Example:
PPHIM01D - a daily PROD job for Philippines for the BANK application
For periodic utility jobs such as monthly backup, the 7th and 8th character of the jobname must be as
follows:
MB Monthly Backup
MR Monthly Restore
YB Yearly Backup
YR Yearly Restore
QB Quarterly Backup
QR Quarterly Restore
HB Half-yearly Backup
HR Half-yearly Restore
Example:
PPHFM9MB - Monthly backup job for Philippines FMS application.
4.3.1. Job Names -- Cards

The following tables contain the specified job name details of all applications supported by RCC.
Job Name Details
REQ - enter Y = Require

N = Not Applicable
BEHAVIORIAL SCORING
JOBNAME REQ FRE DESCRIPTION REMARKS RANGE OLD NAME

PccBH01D Y D Behavior score extraction 00-49 PccBSD01
PccBH51D Y D Copy file to mth end file 50-99 PccBSD02
PccBH52M Y M Behavior score month end job PccBSM01
PccBH53D/A Y D/A Behavior score reporting PccBSD03
CACS JCLs
JOBNAME REQ FRE DESCRIPTION REMARKS RANGE OLD NAME

PccCA10D D Daily spool splitter - - PccZTDS
PccCA20D D Daily extract PccCACS1
PccCA30D M Daily update PccZTDU
PccCA35D D Daily print PccZTDP
PccCA40D D Daily report PccZTDR
PccCA50W W Weekly report PccZTWU
Please note the following changes to JCL PROCS standard:
1. Do not use Characters I and ‘O’ (as it looks the same as 0 and 1).
2. Use BBB - before batch backup

ABB - after batch BATCH backup
AOB - after batch ONLINE backup
3. Please note that A1 to AZ is reserve for common backup job BUT not for country specific. For
country specific backup job, follow country specific job naming standard.
October 15, 1997 20

4. Following Data warehouse job name should be changed as it is now under individual
application teams.
5. Add R, T - Reporting
U, V - Upload
X, Y - Download
W - Data Warehouse
6. Job PccCPEWB, PccCPMEB, PccCPVOB, PccCPYEB will be changed as not according

to standard.
7. OPER.MCM.JCL.PARMLIB
For those country which is currently using this library, please remember to stage
members in this library to SPxx.MGB.UPM library for user control parm and
SPxx.MGB.PRM for system control parm.
8. CACS/RMS/NAS regular RE-ORG/Archival job. Please provide mapping new job name
for these jobs and include in the standard job name list.
4.4. Proc Naming Standards
All Production procedures be up to 8 characters long, and have the following format:
AADDDDDD
where:
AA - denotes the Application Identifier
DDDDDD - will be a 6 character description of the procedure.
For country specific/standard utility PROCS:
AACCDDDD or AACCFFDD
where AA - Application ID
CC - Country ID (GB for Global)
DDDD - will be a 4 character description of the procedure
or FFDD - when standard utility program is used
FF = Utility ID, ID = IDCAMS
SR = SORT
IE = IEBxxxx, ICExxxx utility
AR = Inline backup (ARCINBAK)
AS = other backup utility
AF = AF/Operator
AC = ACR Plus
SA = SAS related
XF = XCOM or other file transfer utility
DD = will be a 2 character description of the procedure (use sequential running
number)
October 15, 1997 21

4.5. Parmlib Member Naming Standards

All Production JCL parameter (parmlib) members must be at least 5 characters long. These members are
static and are not required to be changed for the day to day running of the batch run. Any changes to
parmlib members are made through a request via CHANGE-MAN. A parmlib member contains control
statements that is input to Utility programs such as IDCAMS and IEBGENER. Parmlib members have the
following format:
AAFFDDDD
where:
FF - pertains to the parmlib function
They are:
DL - To delete one or more datasets
DF - To define one or more datasets
RE - To copy from one dataset to another
SR - To contain parameters for a sort routine
IE - Parameter for IEBxxxx or ICExxxx utility
AL - Alter one or more data set
BI - Build Indexes
VF - Verify one or more data set
PR - Print one or more data set
PG - Program SYSIN card
NB: If a parmlib member contains delete and define control statements then you should enter DF
as the third and fourth character of the member name.
DDDD - will be a 4 character description of the parmlib member. This is often made up
from the first 4 characters of the dd name.
or
For Country specific PARMLIB:
AAFFCCDD
where:
FF - pertains to the parmlib function
They are:
DL - To delete one or more datasets
DF - To define one or more datasets
RE - To copy from one dataset to another
SR - To contain parameters for a sort routine
IE - Parameter for IEBxxxx or ICExxxx utility
AL - Alter one or more data set
BI - Build Indexes
VF - Verify one or more data set
PR - Print one or more data set
PG - Program SYSIN card
CC - country ID (BG for Global)

DD - will be 2 character description of the PARM member,
use sequential running number
NOTE:
GRBRESET - standard PARM member to reset IDCAMS return code
(same as RESETCC member)
October 15, 1997 22

4.6. USER Parameter Naming Standards
A Userparm member is one that contains modifiable data that is input to Application programs, e.g. Data
parameters. These modifications are normally updated by the User.
Userparm members have the following format:
AADDDDDD
where:
DD - is for description that can be up to 6 characters long.
October 15, 1997 23

5. OPERATIONS ACCEPTANCE STANDARDS
The main objectives of the Operations Acceptance Standards (OAS)

are:
1. To ensure that application batch runs are run with maximum automation, minimum operator’s intervention and
zero processing error.
2. To prevent unnecessary application abnormal endings (ABENDs) and programmer’s intervention.
All new systems and major modifications to existing systems must comply with the Operations Acceptance
Standards (OAS) before they are accepted for Production.
The following describes the main areas the systems must comply:
5.1. File Transfer

(a) The operator should not be required to manually activate any file transfer.
(b) There must be an alert message to indicate unsuccessful file transfer.
(c) There must be automation to check that the number of records have been transferred correctly before
starting the batch string.
5.2. File Control for Bank (Systematics) Applications

- There should be no manual input by operators. Data such as controls, which are required for
processing should be fixed or generated by the applications or input by users.
- - Batch jobs for processing interface input files should be automatically triggered upon
successful receipt of input files. This can be done using a CICS program, XCOM, AF
OPERATOR and OPCA. A CICS program can be automatically started off once the XCOM has
completed the task of transferring the file. The CICS program reads the history record from XCOM
for the status of the transfer and the number of records transferred. If the status is good, the
CICS program will then output a console message for AF OPERATOR. The AF OPERATOR then
kicks off the jobs by calling the OPCA.
- All input files should be defined on disks, except for external input. All external input tapes should be
preferably standard labeled and subjected to the same control checks as per (b). Any exceptions
must be justified and documented with compensating controls.
- All interface files should have the header and trailer records (see Appendix E for suggested layout of the
header and trailer records). All interface input files must contain at least the header and trailer records
even if there is no data record.
The following checks should be performed by the respective application using the header/trailer records
before using the files for further processing during batch run.
5.2.1. Checking For Data Integrity Of Files
i) Processing date in header record must be same as business

date (use the SAS current date or the
IMBCR date). If not the same, the program should set return code to 999 and display
an error message, for example:
‘PROCESSING DATE IN HEADER RECORD DOES NOT MATCH BUSINESS DATE’

‘PROCESSING DATE IN HEADER RECORD = CCYYMMDD’
‘BUSINESS DATE = CCYYMMDD’
October 15, 1997 24

ii) Hash amount computed by program must tally with the hash amount from the trailer record.
If discrepancy exists, the program should set return code to 999 and display an error message, for
example:
‘HASH AMOUNT COMPUTED DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘HASH AMOUNT FROM FILE = 9,999,999,999,999.99’
‘HASH AMOUNT COMPUTED BY PROGRAM = 9,999,999,999,999.99’
iii) Total number of records processed (including header and trailer) by the program must tally
with the record count in the trailer record. If discrepancy exists, the program should set return code to 999 and
display an error message, for example:
‘TOTAL RECORD COUNT DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘TOTAL RECORD COUNT FROM FILE = 999999999’
‘TOTAL RECORD COUNT PROCESSED BY PROGRAM = 999999999’
iv) If account hash is present, account hash computed by program must tally with the account
hash from the trailer record. If discrepancy exists, program should set return code to 999 and
display an error message, for example:
‘ACCOUNT HASH DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘ACCOUNT HASH FROM FILE = 999999999’
‘ACCOUNT HASH COMPUTED BY PROGRAM = 999999999’
5.2.2. Checking for Duplicate Processing

A control file is to be maintained by application where the following information from all interface
input files for the last 30 days (the retention period is variable depending on application
requirements) are kept:
- Filename
- Creation date
- Creation time
- Hash amount
- Record count
- Account hash
The above fields form the key for the control file. For every input file processed, a record is
written to the control file using the above data from the input file.
October 15, 1997 25

A check against the control file will be done using the above data from the trailer record of each
input file. If existing record is found, it indicates the possibility of duplicate processing for the
input file. The program should then set the return code to 999 and display error messages:
‘DUPLICATE PROCESSING OF INPUT FILE, PLEASE CHECK’

‘CONTROL FILE KEY = XXXXXXXX CYYMMDD HHMMSS HHHHHHHHHHHHHHH
RRRRRRRRR AAAAAAAAA’
where XXXXXXXX = Filename

CCYYMMDD = Creation date
HHMMSS = Creation time
HHHHHHHHHHHHHHH = Hash amount
RRRRRRRRR = Record count
AAAAAAAAA = Account hash
5.3. File Control for Cards (ECS) Applications

In order to prevent duplicate processing and ensuring data integrity of files, all interface files to ECS must
contain header and trailer records (see attached Appendix J for record layouts) for file control. Similarly,
all output files from ECS to banking system must also contain header and trailer records. All data records
will be embedded between the header (first record) and trailer (last records) records in the interface files.
All interface input files must contain at least the header and trailer records even when there is no data
record for the run.
All interface files should be defined on disks. Under special conditions whereby interface files have to be
defined on tape/cartridge, they must be defined as standard label and the application should not use the
option to bypass label checking during the processing of the tape/cartridge.
The following checks should be performed by the respective application using the header/trailer records
before using the files for further processing during batch run.
5.3.1. Checking for data integrity of files

I) Processing date in header record must be same as business date (use next processing date in
CPBSYS if input file is processed before CPD090 or today’s date if input is processed after
CPD090). If error, program should set 999 in return code and display an error message, for
example:
‘PROCESSING DATE IN HEADER RECORD DOES NOT MATCH WITH BUSINESS DATE’
‘PROCESSING DATE IN HEADER RECORD = YYYYMMDD’
‘BUSINESS DATE = YYYYMMDD’
ii) Hash amount computed by program must tally with the hash amount from the trailer record.
If discrepancy exists, program should set 999 in return code and display an error message,
for example:
‘HASH AMOUNT COMPUTED DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘HASH AMOUNT FROM FILE = 9999999999999.99’
‘HASH AMOUNT COMPUTED BY PROGRAM = 9999999999999.99’
October 15, 1997 26

iii) Total number of records processed by program must tally with the record count in the trailer
record. I f discrepancy exists, program should set 999 in return code and display an error
message, for example:
‘TOTAL RECORD COUNT DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘TOTAL RECORD COUNT FROM FILE = 999999999’
‘TOTAL RECORD COMPUTED BY PROGRAM = 999999999’
iv) If account hash is present, account hash computed by program must tally with the account
hash from the trailer record. If discrepancy exists, program should set 999 in return code
and display an error message, for example:
‘ACCOUNT HASH DOES NOT TALLY WITH FILE, PLEASE CHECK’
‘ACCOUNT HASH COMPUTED BY = 999999999999999999’
‘ACCOUNT HASH FROM FILE PROGRAM = 999999999999999999’
5.3.2. Checking for duplicate processing

A control file is to be maintained by application whereby the following information from all
interface input files for the last 30 days (the retention period is variable depending on application
requirements) are kept:
- Filename
- Creation date
- Creation time
- Hash Amount
- Record Count
The above fields will form the key for the control file. For every input file processed, a record will
be written to the control file using the above date from the input file. A check against the control
file will be done using the above data from the trailer record of each input file. If existing record is
found, it indicates the possibility of duplicate processing for the input file. In this case, program
should set 999 to return code and display an error message, for example:
‘DUPLICATE PROCESSING OF INPUT FILE, PLEASE CHECK’

‘CONTROL FILE KEY = XXXXXXXX YYYYMMDD HHMMSS HHHHHHHHHHHHHHH
RRRRRRRR AAAAAAAAAAAAAAAAAA
where XXXXXXXX = Filename

YYYYMMDD = Creation Date
HHMMSS = Creation Time
HHHHHHHHHHHHHHH = Hash Amount
RRRRRRRR = Record Count
AAAAAAAAAAAAAAAAAA = Account Hash
5.3.3. Algorithm for Hash Total Computation
The algorithm is based on Modulus-10 method. If source amount is

less than 15 digits, pad source amount with leading zeroes
before applying the algorithm.
Example: Source amount = 538400021479
0 0 0 5 3 8 4 0 0 0 2 1 4 7
9
x x x x x x x x x x x x x x
October 15, 1997 27

2 1 2 1 2 1 2 1 2 1 2 1 2 1
2
______________________________________________________________________________
0 0 0 5 6 8 8 0 0 0 4 1 8 7
18
0 + 0 + 0 + 5 + 6 + 8 + 8 + 0 + 0 + 0 + 4 + 1 + 8 + 7 + 1 + 8 = 56
56  10 = 5 remainder 6
10 - 6 = 4
4 x 56 = 224 <-- Hash Total
5.4. Online
- All input data via online transactions should be validated by application to ensure that there will be
no exception error during batch run.
- Application messages should not be written to the system console except those standard format
messages used for automation like messages for AF OPERATOR.
- Online programs when abnormally ended (ABEND) should be handled by application with appropriate
messages displayed to end-users, or to the appropriate recipient of messages. Similarly when
exceptional conditions occur.
- Batch jobs must not be submitted from online programs.
- All online update programs should use dynamic transaction backout or rollback to ensure file
integrity when programs abnormal ended (ABEND).
- Application teams should review CICS log (from TSO) during testing and UAT to detect any storage
violations or abnormally endings (abends). These violations and abends should be resolved before
cutover to production.
5.5. Batch
5.5.1. Application Design Consideration
- There must be no manual checking of return codes by the operator.
- Criteria for successful batch job/step should always be set to zero. (Exceptions where
non-zero return codes are acceptable must be justified and documented).
- Batch programs must be able to check and handle empty input files without operator
intervention.
- Application programs should be able to detect duplicate processing of the same input file.
- For very long running programs, messages should be displayed to show the various
milestones in the processing. This helps to determine any problem in the processing like
contention for resources.
5.5.2. Archival/Housekeeping
- All batch input files should be deleted during batch processing. This is normally done in the
jobstep prior to the step which creates each subsequent files.
Note : Yesterdays input batch files otherwise no files to process with.

- Intermediate files should be deleted immediately upon successful job completion.
- Application design must incorporate the routine archival of historical records.
October 15, 1997 28

5.6. AF/Operator Automation

AF/Operator is the tool from Candle Corporation used to automate manual intervention by Operator during
batch run. Automation includes Opening/Closing of files and issuing of certain CICS transaction in UAT
and Production environment only.
It basically intercept WTO messages sent to the Console from systems, CICS transaction or batch jobs.
AF/Operator makes use of TRAPS and ‘EXECS’ to perform the automation task.
The interaction to CICS Application is via the Programmerless Open Vtam Interface (POVI).
5.6.1. System Setup

AF/Operator is installed on both the UAT and Production system.
The started task name is
xDCAFOPE - AF/Operator started task

xDCAFOVI - POVI
where x is either ‘P’ for Production or ‘A’ for UAT
5.6.2. Traps & Execs
Traps and Exec’s are stored in the following PDS :-
SxSY.MAF.CMDLIB
where x is either ‘P’ for Production or ‘A’ for UAT
Traps member begin with ‘T’ whereas EXEC member name(s) begin with ‘C’.
5.6.3. Message Trapping & Automation

AF/Operator trap for this console message which is submitted via batch job.
The format of the WTO must conform strictly to this standard:
‘AFCIx &member *’
where x should be ‘F’ for files and ‘T’ for transaction
Example of JCL coding to issue the WTO message can be found below.
//STEP020 EXEC PGM=IPOWTO,

//PARM=‘AFCIF BPHCIO0X - OPEN RF*,RBP*’
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=80,BLKSIZE=800)
//SYSIN DD DDNAME=IEFRDER
//IEFRDER DD DUMMY,DCB=BLKSIZE=80
//*
Member name must be unique and Programmer must provide to Production Controller all the
‘CEMT’ commands and the files to Close/Open or the transaction name to be invoked. Each
country will have its own PDS to store the Parameter members. For example, all automation
member for Philippines ICBS will be stored in this PDS:
‘SAPH.MAF.PARMBANK’
The EXEC ‘CDCICFL1’ will be triggered and perform the following task :-
- Logon to respective Country CICS.
October 15, 1997 29

- Read the member which store the commands to Open/Close files or invoke a
transaction in CICS.
5.7. Console Message Naming Convention
5.7.1. External CICS Interface

EXCICLN1 is a utility program to close and open CICS files as well as starting a CICS
transaction via a batch job. The utility was written using External CICS Interface (EXCI) protocol.
When EXCICLN1 is executed from a batch job, it establishes a session with a server program,
EXCISRV1, in the target CICS system. The server program will issue appropriate CICS command
according the parameters passed from EXCICLN1.
5.7.1.1. Invoking EXCICLN1
Below is a sample job to initiate the utility.
//jobname JOB (APCC),'comment',CLASS=c,MSGCLASS=X,NOTIFY=userid,

// MSGLEVEL=(1,1)
//STEP1 EXEC PGM=EXCICLN1,PARM='applid,function,parm1,........,parm8'
//*
//STEPLIB DD DISP=SHR,DSN=SADC.MCM.LOD.AE41.BASE0
// DD DISP=SHR,DSN=CICS410.SDFHEXCI
// DD DISP=SHR,DSN=CEE.V1R3M0.SCEERUN
//SYSPRINT DD SYSOUT=*
//*
5.7.1.2.Parameters for EXCICLN1
applid = CICS' applid where the action will be taken
function = OP open and enable the specified files

CL close and disable the specified files
EN enable the specified files
DI disable the specified files
parm1 - parm8 = For function = OP or CL;
File names to be closed or opened, up to 8 can be specified. If more than 8 file names are
specified, the excess is ignored. Both specific and prefix file names are acceptable
eg. .......,ABAUD,CA*,......
To continue the parameter to the next line, extend the parameter to column 71. Enter a
non blank character in column 72 (do not use ' ). enter // in column 1 and 2 in the next line
and continue the parameter from column 16.
EXAMPLE :
//EXCICJCL JOB 'EXCI',MSGCLASS=X,MSGLEVEL=(1,1),CLASS=A

//*
//PROCLIB JCLLIB ORDER=(SAIN.MSI.PRC.CMPRM,SARB.MSI.PRC.CMPRM,
//
SAIN.MCM.PRC.INSI.BASE0,SARB.MCM.PRC.RBSI.BASE0)
//*
//SETVALUE SET JLIB=SAIN,CTRY=IN
// INCLUDE MEMBER=ARBSIPRC
//*
//*--------------------------------------------------------------------
//* EXCI : AINCICI - CLOSE FILES
October 15, 1997 30

//*--------------------------------------------------------------------
//*
//AAEXCIBB EXEC AAEXCIBB,
// CC=IN COUNTRY CODE
//*.....
October 15, 1997 31

//*
//AAEXCIBB PROC CC=RB COUNTRY CODE
//*
//* NOTE : X at column 72, and continue parm must start from column 16
//*
//STEP010 EXEC PGM=EXCICLN1,
//
PARM='A&CC.CICI,OP,FMACT01,FMAC201,FMRCR01,FM*,ACCT*,FMCCR01,X
// FMHSR01'
//*
5.7.1.3. Return Codes

RC = 0 transaction initiated OK, file(s) closed/opened successfully
5 not all files closed or opened files that failed to open/close is
listed in the job log, with reasons;
N = file not found
A = not authorised
I = invalid requested, most likely the dataset does not exist
6 too many files failed to open/close ( > 100 )

7 invalid function
8 file/transaction not found
12 not authorised
16 invalid requested, most likely the dataset does not exist
99 system error, contact APCC SP
5.7.2. CLOSE/OPEN CICS ONLINE FILES

AFCIF yxxddzzz
where y is P for card

B for bank
G for PBG
xx for Country code
dd for Application code
do for dinner application
zzz for Unique code
yxxzzzzz is a member name contain number of cemt command to perform

OPEN/CLOSE FILES
yxxzzzzz has to be created at SPxx.MAF.PARMyyyy library
where yyyy CARD for card

BANK for bank
PBG for PBG
5.7.3. Trigger CICS Transaction

AFCIT yxxzzzzz
where:
y is P for Card
B for Bank
October 15, 1997 32

G for PBG
xx for Country Code
dd for Application Code
do for Diner’s Application
zzzzz for unique code
October 15, 1997 33

yxxzzzzz is a member which contains:
tttttt nn mmmmmmmm
where:
tttttt Transaction name and parm (e.g.: TSPH#SER#1234) (Note the delimiter
between the transaction and parm is # and the maximum number of
delimiters allowed cannot exceed two.)
nn Line number to display completion message

where:
yyyy is Card for Cards
Bank for Bank
PBG for PBG
5.7.4. Submit Batch Job

AFBAT yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx for Country code
dd for Application Code
do for Diner’s Application
yxxzzzzz is a member which contains the following commands:
‘S AFJOB,D=xxxxxxxx,N=yyyyyyyy’
where:
xxxxxxxx is the name of the library which contains the job
yyyyyyyy is the job name
where:
Bank for Bank
PBG for PBG
5.7.5. XCOM File Transfer

AFXCM yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx for Country Code
‘S AFJOB,D=xxxxxxxx,N=yyyyyyyy’
where:
October 15, 1997 34

xxxxxxxx is the name of the library which contains the job

yyyyyyyy is the job name
where:
Bank for Bank
PBG for PBG
5.7.6. Page For The Assigned Person When The Critical Job Abend
AFJOB yxxzzzzz
where
y is P for card
B for bank
G for PBG
xx for Country code
zzzzz for Unique code
yxxzzzzz is a member name contain the following information
'xxxxxxx yyyyyyyy'
where
xxxxxxxx for Pager no.. eg. 93003451
yyyyyyyy for Assigned Person eg. Ali Ba Ba
where
yyyy for CARD for card
BANK for bank
PBG for PBG
5.7.7. Monitor LU
DFHZNEP xx yyyyyyyy zzzzzzzz comments

where:
yyyyyyyy CICS - ID
zzzzzzzz LU net-id
xx Blank
The LU to be monitored has to be coded in SPSY.MAF.CMDLIB(PDCVTDB).
Enter ‘EX CDCVTRD1’ at the console after updating PDCVTDB to enable monitoring.
5.7.8. Start OASM Transaction
October 15, 1997 35

AFCIA yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx Country Code
dd Application Code
do Diner’s Application Code
zzzzz Unique Code
yxxzzzzz is a member which contains the following options and messages:
‘xx yyyyyyyy’
where:
xx is for option and
yyyyyyyy is for reply message(s)
yxxzzzzz has to be created in SPSY.MAF.PARMyyyy library
where:
yyyy Card / Bank / PBG
5.7.9. Issue Operator Commands

AFOPR yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx Country Code
zzzzz Unique Code
yxxzzzzz is a member which contains the following operator commands:
where:
yyyyyyyy is for operator command(s)
October 15, 1997 36


where:
yyyy is for Card / Bank / PBG
5.7.10.Startup CICS
AFCIS xxxxxxxx
where:
xxxxxxxx is the CICS-ID
5.7.11. Shutdown CICS

AFCIE yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx Country Code
zzzzz Unique Code
xxxxxxxx related to the CICS-ID
yxxzzzzz is a member which contains the CICS Shutdown commands:
yxxzzzzz has to be created in SPSY.MAF.PARMyyy library
where:
5.7.12.File Transfer Automation

AFXCS message will be triggered by PCDX transaction
AFXCS yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
xx Country Code
zzzzz Unique Code
October 15, 1997 37


‘S AFJOB,D=xxxxxxxx,N=yyyyyyyy
where:
xxxxxxxx is the library name which contains the job and
yyyyyyyy is the actual job name
where:
AFXCE message will be triggered by PCDC transaction
AFXCE yxxzzzzz
where:
y is P for Card
B for Bank
G for PBG
AFXCF xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If the XCOM does not get triggered then the AFXCF message will be displayed on the CONSOLE
to alert the Operator(s).
5.7.13.Load NCP
AFNCP yxxzzzzz
where:
yy always ‘P’
xx Country Code
zzzzz Unique Code
yxxzzzzz is a member which contains the VTAM commands:
For loading of NCP the first 2 bytes have to be ‘L’
e.g.: ‘L V NET,ID=PDCNCP2,LOAD=YES’
yxxzzzzz has to be created in SPSY.MAF.PARMSYS library

5.8. JCL Standards
5.8.1. Jobs
Options available to the Data Center (DC) regarding parallel execution possibilities are also more
visible with more and smaller jobs as opposed to fewer jobs containing more steps. Where
parallel processing is possible it should be clearly documented to ensure maximum use is made
of the resources available. This will optimize the batch run for the minimum amount of elapsed
time.
All JOBS must be in PROC format.
If a multi-step long running job requires a CART drive for one step, this step should be a separate
job. OPC/ESA allocates CART drives for an entire job within its workload balancing.
JCL will NOT have any comments line except for RECOVERY purpose, these statement should be
placed on top of the PROCS step statement.
5.8.2. Jobcard
The JOB card should not be coded beyond column 68. Columns 69-71 are used by OPC/ESA to
identify jobs under OPC control.
October 15, 1997 38

5.8.3. Parm Field
The use of Parm field should be avoided. The PARM field in the EXEC statement of the JCL
should only be used for static data which is not or seldom changed.
Note: Dates, exchange rates, and similar input should come from an application dataset, or from
control card input.
5.8.4. Catalogued Datasets

Datasets used in the procedure should be catalogued. The only exception are work datasets used
only in one step of the procedure. Datasets being created should use the disposition of
(NEW,CATLG,DELETE). This will delete datasets should the particular step abend.
5.8.5. Sort Work Files

Dynamic allocation of sort work file is preferred as the sort program will allocate work space to get
the best possible performance. However, if a sort requires greater than 50,000 bytes of sort
space, sort work DD statements must be added to the sort step. (please refer to Chapter 9
section 5 SORTWK limitations and recommendations)
5.8.6. Operator Replies

Application programs should never be dependent on the presence of a computer operator to
provide a reply to questions on the console.
5.8.7. Definition of the External File Interface

- Any file uploaded/downloaded via XCOM, other FTP software or TAPE from outside
sources.
October 15, 1997 39

- Any file handed off or received from NON BANK systems. This would include files to/from
CARDPAC and PC based MIS, CALM etc. systems.
- The use of HEADER/TRAILER is encouraged, but not required for INTERNAL interfaces
such
as for example between IMPACS and FMS etc.
5.8.8. External System Interfaces

Any external interface files between systems should be GDG based. A limit of 2 cycles must be
kept.
5.8.9. Temporary Files

Datasets that get created during a job and used for the duration of that job only, are regarded as
temporary files. These files will be written to work packs to conserve space on the production
volumes. Files residing on work volumes are deleted on a daily basis.
Temporary datasets should not have a disposition of PASS if they are not used again within the
job creating them. This confuses the rerun/restart package as it counts the number of temporary
datasets being created and deleted during the execution of a job. Any steps that run after a
temporary dataset is created, but before it is deleted are deemed non-restartable. The last
reference to a dataset should have DELETE as their 2nd and 3rd delimiters in the disposition field
of the dd statement.
5.8.10.PROCS Override
If you need to override file attribute in the DD card, in the calling JCL, specify the affected
attribute ONLY.
E.g. If you need to change record length for file CPAUTH
//CPD050.CPAUTH LRECL=122
If you need to override the DD card, in the calling JCL, specific full DD card affected.
E.g. If need to change CPTUI input in CPD030
//SRTC030.SORTIN DD DSN=&HLQ..BNA.NAMAINT *NAS

// DISP=SHR
// DD DSN=&HLQ..BCP.CPTUI.INS, *INSURANCE
// DISP=SHR
// DD DSN=&HLQ..BCP.CPTUIM, *CARD UPGRADE
// DISP=SHR
5.8.11.Variable List for Library

&PRMLIB = PARMlib variable
&PRMUSR = User PARMlib variable
5.8.12.Include Member
INCLUDE member with naming standard as:
PccaaPRC will be used to set the require Loadlib and PROCS variables
This include member will be placed in the JCL library.
5.8.13.Calling JCL, PROCS Statement

In the calling JCL, PROCS statement will be coded as
October 15, 1997 40

//AECPD008 EXEC PROC=AECPD008

PROC= to be coded for each PROCS statement, this is for easy reference
5.8.14.Qualifier
The HLQ, HLQ1, HLQ2 variables will be required for card due to the various library required
e.g. SPcc - country library

SPGB - Global library
SPWA - West Asia library
5.8.15.Reference
Following list will be available for reference:
- JCL list refer to STGB.MCP.JCL

- PROCS list STGB.MCP.PRC
- Utility list STGB.MCP.UTL
- PROCS Variable list * STGB.MCP.JCL (PaeCPPRC)
- PRM list STGB.MCP.PRM
* PaeCPPRC will contain all common PROCS variable, however there will be other job
related variables (such as record length etc.) which are specified in the individual
PROCS.
5.9. Rerun
5.9.1. Restart Overview

The rerunning of batch jobs is controlled by OPC/ESA. It will decide where jobs can be restarted
and adjust the JCL in a restart situation. Any files that will be recreated will be uncatalogued and
scratched.
The following rules should apply when setting up a batch Job:
(a) It is recommended that a backup of any files being updated be available. This will enable
restoration of files in problem situations and expedite the time it takes to rerun the abended
job.
(b) When a program deliberately abnormally terminates (ABENDs), there should be error
messages to identify the problem and the milestones in processing. The messages should
have the number of records already processed, the file that is causing the problem and the record that is causing
the problem.
5.9.1.1.Manual JCL Override

1. To restart a particular step within instream data you would need to override the job
statement as follows:
,RESTART=STEPNAME
2. To restart a particular step within a procedure you would need to override the
job statement as follows:
,RESTART=STEPNAME.PROCSTEPNAME
October 15, 1997 41

An example is listed below
JCL:
//AINAM15D JOB ‘ALS’, CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
// RESTART=STEPNAME.PROCSTEP
//*
//*--------------------------------------------------------------------------------
//* BATCH NEW ACCOUNT PROCESSING
//*--------------------------------------------------------------------------------
//*
//STEPNAME EXEC AMP015D,
// HLQ=SAIN,
// GRP=I33,
// SPME=‘(CYL,(10,10),RLSE)’
//
PROC:
//*--------------------------------------------------------------------------------
//* BATCH NEW ACCOUNT PROCESSING
//*--------------------------------------------------------------------------------
//*
//AMP015D PROC HLQ=SARB,
// GRP=IRB,
// SPME=‘(CYL,(10,10),RLSE)’
//*
//*----------------------------------------------------------------------------------
//* DELETE/DEFINE X-REFERENCE FILES
//*----------------------------------------------------------------------------------
//*
//STEP010 EXEC PGM=IDCAMS,COND=(0,NE)
//SYSUDUMP DD SYSOUT=*
//SYSIN DD DSN=&HLQ..MSI.PRM(AMDF015D),DISP=SHR
//*
//*----------------------------------------------------------------------------------
//* DELETE BATCH NEW ACCOUNT FILES
//*----------------------------------------------------------------------------------
//*
//PROCSTEP EXEC PGM=IEFBR14,COND=(0,NE)
//SYSUT1 DD DSN=&HLQ..AM.AM.&GRP..AMDAT.S15O,
// DISP=(MOD,DELETE),
// SPACE=&SPME
//SYSUT2 DD DSN=&HLQ..AM.AM.&GRP..AMCUT.S15O,
// DISP=(MOD,DELETE),
// SPACE=&SPME
This JOB statement indicates that the system is to restart execution at PROCSTEP in procedure AMP015D.
STEPNAME is the name field on the EXEC statement that calls the cataloged procedure that contains procedure
step PROCSTEP.
3. To substitute a dataset with the DDNAME of FILE1 used in STEP030 in procedure

CPPRC20D you would code the following:
//PROC010 EXEC CPPRC20D

//STEP030.FILE1 DD DSN=SAIN.OVERRIDE.DATA.SET,DISP=SHR
October 15, 1997 42

4. To substitute other dataset parameters within a DD statement you would code

the following:

//STEP030.FILE1 DD SPACE=(CYL,(50,30),RLSE),
NB. The above example is overriding the space parameter for FILE1 in STEP030
within procedure CPPRC20D with a 50 primary, 30 secondary cylinder allocation.
The other dataset parameters do not need to be coded.
5. To substitute a dataset’s concatenation you must code the overriding DD statement

to contain the datasets you want present in your concatenation. Note that if there
are more datasets in the procedure than you are substituting then the unsubstituted
datasets in the procedure would appear at the bottom of the concatenation.
//PROCE030 EXEC CPPRC50D

//STEP030.FILE1 DD DSN=SAIN.OVERIDE.DATA.SET1,DISP=SHR
// DSN=SAIN.OVERIDE.DATA.SET3,DISP=SHR
6. To nullify or exclude a dataset from a concatenation you would code DUMMY on the
overriding statement. The example below would substitute the 1st 2 datasets
and exclude the next 2 datasets from the concatenation within the procedure.

//STEP030.FILE1 DD DSN=SAIN.OVERIDE.DATA.SET1,DISP=SHR
// DUMMY
// DUMMY
NB. When applying multiple overriding statements for different DD’s they must be
placed in the order as seen within the procedure.
7. Jobs that contain nested procedures are able to be restarted. At the moment
however you need to put a restart card on the job statement as there is a bug with
OPC which IBM is looking at currently.
To facilitate the faster recovery of batch jobs, recovery jobs should be built into the production job
streams. For example, for IM31, the IMPACS main posting program, these three jobs are built
into the job stream : PSGIM31B, PSGIM31D and PSGIM31R. The naming convention for
SYSTEMATICS job is : those jobs ending with B are for backup of files before processing, those
jobs ending with D are for the main processing and those with R are for restoration of files from
the backup. If the job PSGIM31D failed, the operator should run the restoration job PSGIM31R
before running PSGIM31D again.
Logical checkpoint/restart should be built into application programs for ease of recovery.
The JCL are coded with the following statements -
5.9.2. OPC - Batch Auto Recovery

A. Step Recovery
//*%OPC RECOVER RESTART=N,ERRSTEP=JOBSTEP.PROCSTEP,
//*%OPC RESSTEP=JOBSTEP.PROCSTEP
October 15, 1997 43

Eg : //PPHIM02D JOB 'IMPACS',MSGCLASS=X, MSGLEVEL=(1,1),

// CLASS=A,COND=(0,NE)
//*
//PROCLIB JCLLIB ORDER=SPPH.MSI.JCL.PRC
// INCLUDE MEMBER=PPHGAPRC
//*
//*%OPC RECOVER RESTART=N,
// ERRSTEP=IMPRSOL.STEP010,
//*%OPC RESSTEP=IMPRSOL.STEP010
//* .....
//*----------------------------------------------------------------------------------
//* ONLINE FILE RESTORE
//*----------------------------------------------------------------------------------
//IMPRSOL EXEC IMPRSOL,
// SOUT=*, SYSOUT CLASS FOR MESSAGES
RESTART=N (Always N because there is a need to check the status before the
recovery can be proceed)
ERRSTEP= Jobstep.procstep (If an ERROR happened for the job in jobstep in
procstep)
RESSTEP= Jobstep.procstep (On the above error do a restart from jobstep in
procstep)
***
If a job failed for Philippines in production at step020. The jcl in OPC 5.4 error log for job
PPHIM02D will be automatically updated with restart=IMPRSOL.STEP020. (The OPC
updated jcl can be view in OPC 6.3 and enter the jobname to view the jcl)
Example : for job failed at step020 and jcls updated
//PPHIM02D JOB IMPACS',MSGCLASS=X,MSGLEVEL=(1,1),

// CLASS=A,COND=(0,NE) ,
//RESTART=( IMPRSOL.STEP020)
//*
//*
//*>OPC RECOVER RESTART=N,
//* .....
//*--------------------------------------------------------------------------------------
//* ONLINE FILE RESTORE
//* OPC MSG:
//* OPC MSG: I *** R E C O V E R Y A C T I O N S T A K E N ***
//*--------------------------------------------------------------------------------------
//IMPRSOL EXEC IMPRSOL,
....
October 15, 1997 44

Check the job and rerun in OPC 5.4.
B. Job Recovery
//*%OPC RECOVER RESTART=N,ADDAPPL=APPLICATIONNAME
Eg: //PPHIM12D JOB
'IMPACS',CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),
// REGION=4098K,COND=(0,NE)
//*
//*
// ERRSTEP=IMPCTL.STEP010,RESSTEP=IMPCTL.STEP010
// ERRSTEP=IMPCTL.STEP020,ADDAPPL=PPHSYRV1M12D
...
//*------------------------------------------------------------------------------------------*
//* THE ABOVE OPTION -
//* ADD APPLICATION PPHSYRVIM12D (PPHIM12R) WHEN
// JOB FAIL AND
//* STOP FOR PROGRAMMER TO CHECK
//*-----------------------------------------------------------------------------------------*
//* CONTROL FILE PROCESSING
//*-----------------------------------------------------------------------------------------*
//IMPCTL EXEC IMPCTL,
October 15, 1997 45

ADDAPPL=APPLICATIONNAME (Whenever the job failed and recovery need to

perform, an adhoc application is added to
OPC and submit as a HOLD job in JES.
The programmer need to investigate the
problem before the restore job can be
release by operation).
***
The same thing apply to job recovery. The only different for the above sample is that at
step020 there is a need to restore files and rerun the whole job.
What OPC does is to add an application to current plan (must pre-setup in opca).
e.g : When job step020 failed, PPHSYRVIM12D is added to current plan which has
the job PPHIM12R submitted to jes spool (typrun=Hold). The programmer was
informed to investigate before the restore can be executed. Rerun job in OPC 5.4.(No
update in jcl due to RESSTEP is not specified)
***
As OPC will delete any datasets whose first reference in a job has a disposition of new, any files that
are created in a step that is conditionally executed, and are not referenced in a previous step within
the job, should be placed in an IEFBR14 step, listing the dataset name(s) with disp=shr, at the
beginning of the job. This is to ensure that the first reference to a dsn within a job does not have a
disposition of NEW as if it has OPC will delete it.
An example of where this is required is when a step checks the current date and then executes a
step to create a dataset if the date is correct. OPC does not know what condition codes each step
will produce, so it will delete the dataset every time the job is run.
5.9.2.1.OPC - Catalog Management

The ‘G’ system OPCC is add with : CATMGT(YES) and CATACT(DELETE).
Each JCL is coded with AutoRecovery parameter for every step recovery procedure.
Catalog Management ONLY activate when a step failed and will uncatalog it
(New,Catalg) for the step.
It is important to code the recovery step correctly.
i.e. : 1. If a job failed and autorecovery parameter not coded, it will delete whatever
newly created dataset.
2. A job with delete in step010 and updating in step020. When catalog

management is set to Y (yes), the restart can start from step020 without
rerun from step010. (Only when new dataset define).
5.10. Procedure Library Specifications

A procedure is a pre-written segment of JCL code that you can include in a job stream.
By using procedures, the amount of JCL coding you have to do is reduced. As a result,
coding errors are less likely to be made. All changes to Proc’s will be made via
Changeman and staged in and promoted through to Production. Please refer to
Changeman section for details.
5.10.1.Procedure Format
The delivered procedures must have the following format:
1. The procedure description segment
2. The procedure statement segment
3. The step description segment
4. The step JCL statements
October 15, 1997 46

5.10.2.The Proc Description Segment

This segment contains a short description of the procedure function. Operation instructions
should not be included.
The following rules apply to the Proc description segment:
* All lines are standard MVS comments (//*...)

* The Proc description segment starts with a line of ‘-’
* The short descriptive test for each keyword starts in column 15 end ends in column 71
* The Proc Description segment ends with a line of ‘-’ followed by a (//*)
Example:
//*-----------------------------------------------------------------------------------------
//* THIS PROC CREATES THE DAILY INPUT FILE FROM
//* THE TWO INTERFACE FILES.
//*-----------------------------------------------------------------------------------------
5.10.3.The Proc Statement Segment

This segment contains the procedure name, procedure statement and all the symbolic parameters
used by the procedure. The following rules apply to the Proc statement segment:
* The procedure name starts in column 3 on the first line

* The ‘Proc’ keyword starts in position 12 on the first line
* The first symbolic parameter starts in position 17 on the first line.
* Each subsequent symbolic parameter starts in column 12 of each line
* All symbolic parameters must have comments. The comments start in column 40.
* Column 72 is left blank
* After the Proc statement a ‘//*’ statement is included.
October 15, 1997 47

The symbolic parameter values should all be given here on the PROC statement and also in the
EXEC statement in the JCL library. This makes the procedure a complete unit and shows how it
has been used without the need to consult the JCL. The following variables are only used within a
procedure as they are the parameters likely to change between UAT and Production
environments. The values in brackets are possible UAT environment options.
HLQ=‘SPPH’, (UAT,SIT) HIGH LEVEL QUALIFIER

CC=‘PH’ COUNTRY CODE
OC=D, (X) REPORT OUTPUT CLASS
GRP=I01, (I01) FILE GROUPING QUALIFIER
SPSM=‘(CYL,(2,2),RLSE)’, SMALL SPACE ALLOCATION
SPME=‘(CYL,(10,10),RLSE)’, MEDIUM SPACE ALLOCATION
SPLG=‘(CYL,(35,150),RLSE)’, LARGE SPACE ALLOCATION
SPEL=‘(CYL,(70,50),RLSE)’, EXTRA LARGE SPACE ALLOCATION
SPSP-’(CYL,(135,35),RLSE)’ SPECIAL SPACE ALLOCATION
Note : Space symbolic variables are only required when specific allocations are made within
proc. One or more variables can be used. Therefore the following is a sample of what must be
adhered to.
//PROC010 PROC HLQ=‘SPPH’, HIGH LEVEL QUALIFIER

// CC=‘PH’, COUNTRY CODE
// OC-D, REPORT OUTPUT CLASS
// GRP-I01, FILE GROUPING QUALIFIER
// SPSM=‘(CYL,(2,2),RLSE)’, SMALL SPACE ALLOCATION
// SPME=‘(CYL,(10,10),RLSE)’, MEDIUM SPACE ALLOCATION
// SPLG=‘(CYL,(35,10),RLSE)’, LARGE SPACE ALLOCATION
// SPEL=‘(CYL,(70,50),RLSE)’, EXTRA LARGE SPACE ALLOCATION
// SPSP=‘(CYL,(135,35),RLSE)’ SPECIAL SPACE ALLOCATION
//*
5.11. The Step Description Segment

The function of the step is described in this section. This information is mandatory.
The following rules apply to the STEP description segment

* All lines are standard MVS comments (//*....).
* The STEP description of segment starts with a line of ‘-’.
* The STEP description segment contains a one line STEP description which ends in column 71.
* The STEP description segment ends with a line of ‘-’.
* After the STEP description a ‘//*’ statement is include.
//*-----------------------------------------------------------------------------------------
//* SORT INPUT FILE ON COMPANY NUMBER
//*-----------------------------------------------------------------------------------------
//*
5.11.1.The STEP JCL Statements
The EXEC and DD statements of the procedure are specified in this

section.
The following rules apply to the step JCL statements:

* The STEP name starts in column 3 of the first line following ‘//’.
* The EXEC keyword starts in column 12.
* The DD keyword starts in column 13.
* The COND keyword is mandatory in the EXEC statement.
* Other parameters (e.g. DISP, DCB) begin in column 16.
* Only one keyword on each line is allowed.
October 15, 1997 48

Exception:
* It is permitted to code the DSN parameter and the DISP parameter on the same line.
* Column 72 is left blank.
* Columns 73 to 80 are used for sequencing.
* After the last step JCL statement a ‘//*’ comment should be included.
Example:
//STEP010 EXEC PGM-AMP031,COND=(0,NE),PARM=(PARM1,PARM2)
NB: It is preferable to have the Region card on the job statement.
5.11.2.The EXEC Statement

STEPNAME Mandatory. Must be STEP010, STEP020, STEP030, etc. (increment of 10).
Any new steps may increment by 5 (e.g. STEP015), and if further statements
are required may increment by 1 (e.g. STEP016, STEP017).
PGMNAME Mandatory. (It is not symbolic).
REGION Not allowed, except for utilities with non-standard region size. To be placed on
the job statement if required.
COND Mandatory.
Normally the condition code will be: COND=(0,NE). The step is either successful
in which case the condition code is set to 0 or it fails. Which should result in the
rest of the steps being bypassed.
PARM To be avoided but if necessary it is recommended that they are hardcoded to
avoid the proliferation of symbolic.
TIME Not Allowed.
5.12. Tape Management Standards
* NO BLP or NL tapes are to be used.

* Esoteric for 3490 compression cartridge is “CART”.
5.12.1.Tape Retention Standard

* For all GDG volume datasets specify the EXPDT=99000 subparameter (in the LABEL
parameter), and CA-1 will release the volume, when its cycled out. This is highly
recommended.
* For non-GDG volumes you must specify RETPD=X. (X=number of days volume to be
retained)
* In order to expire a volume on a specific day you may use the Julian date format,
EXPDT=YYDDD, subparameter. OR EXPDT=YYYY/DDD for dates after 31/12/99.
Example: EXPDT=93155 which will expire on 04/07/93
* You must never use the EXPDT=99365 parameter when creating new volumes.
5.13. Backup/Restores
The ADRDSSU Utility program will be used for all Daily, Weekly, Monthly, Quarterly and Yearly Backup’s
and Restores prior to any batch job updates.
Backups should be GDG based and the retention period should be 6 for daily, 5 for weekly, 13 on monthly
October 15, 1997 49

and 10 for annual. Any exception or longer request for legal reason, should be documented and approved
by management.
Below is a layout of the requirements for performing a ADRDSSU Backup.

//*-----------------------------------------------------------------------------------------
//* ADRDSSU - Backup of dataset name/s
//*-----------------------------------------------------------------------------------------
//STEP 010 EXEC PGM=ADRDSSU
//DASD0 DD DSN=HLQ.BSY.application.bkupxxx(+1),
// UNIT=CART,
// VOL=(,,,99),
// DISP=(NEW,CTLG,UNCATLG),
// LABEL=(1,SL,EXPDT=99000),
// DCB=DSCB
//SYSIN DD * DUMP DATASET(INCLUDE
(dataset.name.being.backed.up - )) - OUTDDNAME(DASD0)
- OPT(4)
- TOLERATE(ENQF)
- SPHERE
IF MAXCC = 4 THEN SET MAXCC = 0
//*
Below is a layout of the requirements for performing a ADRDSSU Restore.
//*-----------------------------------------------------------------------------------------
//* ADRDSSU - Restore of dataset name/s
//*-----------------------------------------------------------------------------------------
//STEP 010 EXEC PGM=ADRDSSU
//DASD0 DD DSN=HLQ.BSY.application.bkupxxx(0),DISP=SHR
//SYSIN DD * RESTORE DATASET(INCLUDE
dataset.name.thatwas.backed.up - )) - INDDNAME(DSKIN)
- SPHERE
- REPLACE
//*
5.14. The DD Statements
DCB
Only allowed when creating a dataset. Backward referencing in the DCB parameter (DCB=*...)
is NOT allowed.
BLKSIZE subparameter
For new datasets when DCB with RECFM & LRECL is specified then code BLKSIZE=0 to
maximize the blocksize. Do not use RECFM=U.
For SYSOUT datasets if a DCB is coded, the BLKSIZE must be equal to the LRECL;JES2 will
do its own blocking.
DEN subparameter.
Should always be omitted.
DDname
Application Ddnames should be consistent throughout the application. For more information
refer to ‘DATASETS NAMING STANDARDS’, in this document.
DISP
Allowed
Code DISP=SHR if the dataset is input only
Code all other DISP sub-parameters explicitly rather than the default values.
DSN
Code DSN explicitly. Backward references may not be used.
DUMMY
Allowed.
October 15, 1997 50

LABEL
Only allowed for tape datasets.
The following applies for the label parameter:
Dataset sequence number: optional
Label type : optional
- SL for all MVS tapes
- NL is not allowed.
- BLP not allowed.
Password specification : not allowed
UNIT
No unit parameter is required for DASD.
You may defer a tape mount- i.e., UNIT = (,,DEFER).
3490 subparameter should be used for 36 track devices.
3480 subparameter should be used for 16 track devices.
CART subparameter should be used to request cartridges.
Tape subparameter should be used to request reel tape(s).
VOLUME
Allowed only with the sub-operand SER and/or the sub-operand RETAIN.
Not to be used for catalogued files.
Code all sub-parameters explicitly rather than the default values
e.g. VOL=(PRIVATE,RETAIN,2,3,SER=(123456,234567,345678)
SPACE
Always allocate in cylinders.
Always include the RLSE parameter, to release unused space.
SYSOUT
The SYSOUT class is coded to define a dataset as a system output or a sysout dataset
determined by the classification of the report. (Refer to the Sysout Statement section
of this document).
5.15. Application Documentation

All documentation is to be supplied in Microsoft Word Format. This includes Job/Step Restart procedures,
Job Scheduling information, Application documents, Program descriptions, Special Instructions, On-call
procedures and Report Distribution.
The production controllers can refuse to accept changes if jobs are not considered to be adequately
documented.
October 15, 1997 51

The skeleton for Data Center Documentation follows:
5.15.1.Application Overview
1. System Overview
2. Interfaces and restrictions
5.15.2.System/Application Flow Chart
5.15.3.On Call Procedures

5.15.4.Data Center Operations Job Documentation
For a template of the job recovery documentation see Appendix F. An example follows:
Job Recovery Documentation
JOB NAME = = > PPHFM10D ISSUE DATE = = > 23/12/95

PROC NAME ==> FMP1100
STEP NAME ==> STEP010
Recovery Procedure
Rerun from the start of the job

OPC Scheduling Requirements Template
JOB FUNCTION
Verify the input file from the Stratus, for run to run control.
CRITICAL TO ONLINE ENVIRONMENT (Y/N) ==>
RUN FREQUENCY (DAILY/WEEKLY/MONTHLY/YEARLY/REQUEST) = = > Daily
DAY OF WEEK = = > FORMAT (SUN/MON/TUE/WED/THU/FRI/SAT)
DAY OF MONTH/YEAR = = >
TIME SCHEDULED ==>
TRIGGERED BY JOB = = > PPHFM00D
JOB REQUIREMENTS - (PREDECESSORS)

(1) (2) (3) (4) (5)
(6) (7) (8) (9) (10)
TRIGGER JOB/S - (SUCCESSORS)

(1) PPHFM01B (2) (3) (4) (5)
(6) (7) (8) (9) (10)
JOB REQUIREMENTS - (PREDECESSORS)

(1) (2) (3) (4) (5)
(6) (7) (8) (9) (10)
TRIGGER JOB/S - (SUCCESSORS)

(1) (2) (3) (4) (5)
SPECIAL INSTRUCTIONS
October 15, 1997 52

A message is displayed at end of job. Stratus box operators need to be informed that fm tser
extract is ready for transmittal to Stratus box.
Data Retention Scheduling
FILE(S) TO BACKUP : STPH.IM.OC.IMACT.V31
BACKUP RETENTION = = > (Each Backup Generation must be kept for a period of 4 weeks.)
GDG LIMIT = = > (Limit of 5 GDG’s for Backup Datasets.)
5.15.5. Report Distribution (Control-D Requirements)
This is the final section in the Data Center Documentation. Refer to Appendix G for its template. The Report Distribution
was formerly a part of the DC Operations Job Documentation section. To make reference of printed reports much easier,
the RDs from each Job Documentation were consolidated into one under the section named Reports Distribution (Control-D
Requirements).
A sample entry in the Report Distribution table:
START
STEP SYSOUT Line,
JOBNAME No. DDname REPORT NAME RECIPIENT Col
PAEXX04D 030 PRTOUTA LOANS AGING LAHORE DATA CENTER 3,55 - 65
-Loans Department
October 15, 1997 53

Using a sample JOB and PROC, the following explains how to fill out the table with the correct
entries.
Report-generating Job:
//PAExx04D JOB .....
//PROCYY EXEC PROCYY ...
REPORT Procedure:
//PROCYY PROC ...
// ...
//STEP030 EXEC PGM=prog1
// ...
//PRTOUTA DD SYSOUT=(,,&OC) ----> “LOANS AGING”
//
1. JOBNAME
PAExx04D is the name of the Job which generates the report.
2. STEP No
This is the step name in PROCYY procedure.
030 is the last 3 bytes of STEP030.
3. SYSOUT DDname
PRTOUTA is the name of SYSOUT DD in step name STEP030 in proc
PROCYY, which tells specifically where the report is generated.
4. REPORT NAME
This identifies a particular report and is usually the report title literals that actually appears
(or printed) on the printout. Specify the report name here as it would appear exactly on the
printout including number of spaces in between, upper case only, or lower/upper case, or any
special chars.
5. RECIPIENT
This tells where the report will go to (user). If and when applicable, both the following
information must be given. Otherwise, the first one will suffice. The second information
makes it possible to further bundle the report(s) into more specific user-recipients.
1. where will the report be printed (region, branch, data center, etc...)
2. user of the report (department)
In cases where the report has two or more users, the above information must be identified
and supplied for each of the users.
The printing scenario for Banking: the reports are generated in APCC, transmitted to the
respective countries and processed by their BARR/PC or AS400 for printing, and finally
distributed to the user.
One country may have one or more BARR/PC or AS400 and these may be dispersed in
more than one physical location. (For PK, it is called a region, for others it may be called a
branch or a data center, etc...)
The user, for now shall mean a department in a location( or region, or branch, or data center).
e.g. Lahore Region Data Center - Loans Dept.
This means the Loans Aging report will go to the Loans Department(user) in Lahore
(location).
6. START Line, Col

This tells where the report name can be found on the printout. It is the start position line and
column of the report name.
e.g. 3,55-65 means that the report name, "Loans Aging", is found on line 3 column 55 to
65 of the report printout.
October 15, 1997 54

line 3 5- - - -+- - - -6-- - -+- - - -7-

Loans Aging
5.16. Output Standards

5.16.1.Output
(a) A control report should be generated to show all reports that are generated by all the
batch jobs. The report should have the record and the page counts.
(b) All internal reports should have the standard report heading (see Appendix C for Non-
SYSTEMATICS standard reports heading and D for SYSTEMATICS standard reports
heading) except for those submitted to external authorities or agencies.
(c) End of all reports should have the line ‘END OF REPORT’.
(d) Reports should always be generated even if they are empty. They must also have the
header ad the ‘END OF REPORT’ line.
(e) The Form Control Buffer (FCB) should be used for special form printing instead of line
count control by application program.
5.16.2.Sysout Statements
The sysout statement is coded to define a dataset as a system output, or sysout dataset. This
statement is used to assign the characteristics of the dataset such as an output class or form
type.
October 15, 1997 55

The following are explanations of output parameters that are to be used.
5.16.3.Parameter Description
* This requests that the output class be the same as that specified on the
MSGCLASS parameter on the job statement.
N ‘n’ is an alphanumeric character ranging from 0-9 or A-Z. A list of these classes
are provided in the ‘Sysout Class’ section.
(D,ccnnnnn) This requests that the output be directed to output class ‘d’, with a report writer of
‘ccnnnnn’, where ‘ccnnnnn’ is broken down into the following:
cc - Country Code
nnnnn - A 5-digit Control/D number provided by the Data Center
An example of a sysout statement writing to Control/D is as follows:
//REPORT1 DD SYSOUT=(PHnnnnn)
where ‘D’ pertains to the output class for Control D in Production.
5.16.4.Remote Printing Limits

A 10 page limit on reports printed from the Host to LAN printers in Head Office to enable Novell
print queues to be effectively managed. Direct Host attached printers are to be installed in Head
Office where print volumes exceed this limit. Host attached remote print have a limit of 5000
lines.
5.16.5.Standard Operations Utilities
(a) XCOM should be used for file transfer on the non-MVS platform.
(b) Connect Direct should be used for file transfer on the MVS platform.
(c) BARR should be used for report transfer.
(d) OPC/ESA should be used for scheduling of jobs.
(e) CONTROL-D should be used for report distribution.
5.16.6.Sysout Deletion
Sysout data in classes other than those covered in section ‘Sysout Class’ and whose creation date
is three days older than the current date will be deleted on a daily basis. Sysout data in the Hold
Queue’s whose creation date is three days older than the current date will be deleted on a daily
basis.
October 15, 1997 56

6. CICS ENVIRONMENTS
6.1. Test CICS Region Changes
SCOPE : Due to the increase of CICS regions in APCC, application development update CICS Tables in
the test regions.
Only PCTs, PPTs and FCTs can be changed by application team, all links, special terminal and printer
definitions will be done by CICS SPs, as the test regions will have autoinstall of normal terminals.
6.1.1. Implementation Requirement
1) Using the 3 char OPIDENT field in the CICS segment in RACF. Only CICS SPs and
application designated ids have these OPIDENT set CSP, OLA, ECS, NAS, RMS, CACS,
GCB, ICS
where CSP - locked by CICS SP
OLA - locked by OLA team
ECS - locked by NAS team
RMS - locked by RMS team
CACS - locked by CACS team
GCB - locked by Singapore GCB team
ICS - locked by ICBS team
2) Other application developers can only have access to CEDC to browse the CSD
3) All active grouplist in the test regions will be locked by the respective teams and CICS SPs
will lock the active lists and non PPT, PCT and FCT groups after initial setup
4) Group naming conventions to be followed strictly.
5) Lock and unlock Groups on active list will be documented in individual region members in
dataset STDC.MDC.RDO.GRP
6) Active group list is the same as the CICS applid
7) Installation of changes done by using CEDA
6.1.2. Process
1) Changes can be done only to groups in active lists.
2) Each CSD has an active list which contains groups which will be installed during a COLD
start.
3) Application team can verify which are the valid groups that they can update, by referring to
the documentation in STDC.MDC.RDO.GRP
4) Application team makes changes to PCTs, PPTs and FCTs using CEDA to the valid lock
groups.
5) To install these changes, use CEDA.
6) For FCTs modifications, application developer has to delete/discard the current active FCT
entry by issuing CEMT I FILE (*), and type a D next to the FCT entry to delete it. Then
CEDA to install the changes.
6.1.2.1.Naming Conventions
The groups naming conventions are to be followed STRICTLY:

For ECS applications
TccaaFCT - where cc denotes country
aa denotes application
October 15, 1997 57

(Files)
SG - Singapore NA
- NAS
TH - Thailand OA - OLA
PH - Philippines CA - CACS
WA - West Asia CP - CARDPAC
SB - Samba NA - NAS
IN - Indonesia RS - RMS
JP - Japan SS - CARDPAC Security
TU - Turkey DN - OLA Diners
GU - Guam GO - GO systems
HK - Hong Kong BC - Bank Card
TW - Taiwan
AE - UAE
PK - Pakistan
OZ - Australia
BH - Bahrain
OM - Oman
LA - Latin America
EG - Egypt
DC - Data Center
TccaaPCT (transactions), TccaaPPT (programs), ccaa denotes as above.
For Systematics Applications
TccGCPPT - where cc denotes country as above
Note : GC is for CITIBANK in-house developed groups, as we do not want to

override Systematic / vendor vanilla groups.
October 15, 1997 58

Vendor vanilla systematic group are :
NXFCT17 NXPCT NXPPT Vendor supplied

ITFCT17 ITPCT ITPPT “
AMFCT17 AMPCT17 AMPPT17 “
IMFCT17 IMPCT IMPPT “
STFCT17 STPCT STPPT “
IFFCT17 IFPCT IFPPT “
TSFCT17 “
CLFCT17 CLPCT CLPPT “
IRFCT17 IRPCT IRPPT “
APFCT17 APPCT APPPT “
IVFCT17 IVPCT IVPPT “
SMFCT17 SMPCT SMPPT “
OWFCT17 OWPCT OWPPT “
RMFCT17 RMPCT RMPPT “
RFFCT17 RFPCT RFPPT “
REFCT17 REPCT REPPT “
ISFCT ISPCT ISPPT “
ZTFC ZTPC ZTPPT “
GNFCTCI GNNLCI “
FMFCTNA FMNALA “
TLPCT TLPPT “
TSICPPT “
SBAFCT SBAPCT SBAPPT Servantis System
TxxNTFCT TxxNTPCT TxxNTPPT Natural Software
TxxADPCT TxxADPPT Adabas Software
TxxGCFCT TxxGCPCT TxxGCPPT Inhouse developed
TxxDEFCT TxxDEPCT TxxDEPPT Inhouse developed
Data Entry
For further documentation on RDO definitions, refer to CICS / ESA RDO definition
guide.
For TOR Regions
All session connectivity will be via the TOR only. Whenever there are any new
transactions defined in the AOR, it must be defined in the TOR as remote, statically
routed to the AOR. The connection and session ids will be documented in
STDC.MDC.RDO.GRP in the individual country CICS region.
In the TOR, the naming convention are as follows:
$TxxCICI1 - MRO/ISC links to banking CICS (TxxCICI1)

defined by CICS SP
$TxxCICS1 - MRO/ISC links to cards CICS (TxxCICS1)

defined by CICS SP
$TxxRPCT - All remote transactions defined in the TOR

defined by application ( static routing )
October 15, 1997 59

It is the same as PCT definitions with additional parameters;
DESCRIPTION - TxxCICI1 TRANSACTION describes which region the trans

is routed to, banking or cards
DYNAMIC - NO Static routing
REMOTESYSTEM - TxxB or TxxC xx country

Test bank CICS
Test card CICS
REMOTENAME - XXXX same as transaction name
6.1.2.2.New Groups To Be Added To The List

There may be new RDO groups requirement, supplied by vendor. These new groups will
be created by CICS SPs and added to the active lists. These requests will be submitted
by application team in the form of a memo.
TEST Changes With SMR Requirement
1. Test Proclibs - SMR raised by application

2. RCT - SMR raised by application
SLA : 1 week ( Upon receipt of complete request)
6.1.2.3.Training, UAT And PRODUCTION Changes
Please refer to APCC CICS Procedure under Chapter 6.2 of this document.
- SMR raised by users or application team
- Changes created using CHANGEMAN process and approved by Pms.
CICS SP will check daily for CICS request. In created member name
(CUATnnn or PPRDnnn) in SADC.MCM.JCL.CUAT.REQUEST (UAT request)
and in SADC.MCM.JCL.PPRD.REQUEST (Prod request). A sample of the
model member are documented in STDC.MDC.CICS.MODELS
- CICS SP will implement the changes with the SMR.

SLA : 3 days (UAT)
SLA : 3 days (Production)
(Upon receipt of complete request)
6.2. APCC CICS Change Procedure

For TEST changes, refer to document on TEST REGION CHANGES which is done by application team.
All UAT and Production changes will have to go through the CHANGEMAN request and approved by the
project managers, i.e., using CUAT or CPRD CHANGEMAN packages.
6.2.1. STDC.MDC.CICS.MODELS
- This PDS provides a model skeleton CICS table for programmer to refer to when creating their
changes in STDC.MDC.CICS.xxxx.REQUEST.
- All programmers has read only access to this dataset.
6.2.2. SADC.MCM.JCL.CUAT.BASE0
- This PDS will have the requester’s UAT changes upon application PM’s approval.
October 15, 1997 60

- Only CHANGEMAN has update access to this dataset.
6.2.3. SADC.MCM.JCL.CPRD.BASE0
- This PDS will have the requester’s UAT changes upon application PM’s approval.
- Only CHANGEMAN has update access to this dataset.
6.2.4. STDC.MDC.CICS.UAT.REQUEST.DONE
- This PDS contains programmer request that has already been processed by the CICS SP.
6.2.5. STDC.MDC.CICS.PROD.REQUEST.DONE
- This PDS contains programmer request that has already been processed by the CICS SP.
6.2.6. Training, UAT & Production

The following provides a guideline for the programmers to any CICS table changes necessary for
the UAT and PROD system.
1. When programmer has a request to update CICS tables, they create a CHANGEMAN
package, package id CUAT for UAT, package id CPRD for production. He then copy the
model from the model PDS and stage the member into the newly created CHANGEMAN
package. The member created in the package should be named according to the package
id number.
The following provides an example of the process:
Example : Programmer A has to add an entry in the Singapore cards UAT CICS
STEP 1 : He creates a CUAT package. Take note of the generated package number,
e.g., CUAT001
STEP 2 : He copies the skeleton table RDADDFCT from STDC.MDC.CICS.MODELS and

stage into the CUAT001 as member CUAT001.
STEP 3 : He edits member CUAT001 and fill in the header information and CICS entries
info as follows:
PROGRAMMER : PROGRAMMER A
CONTACT NO. : 328xxxx
IMPLEMENTATION DATE : 08/08/96
CICS SYSTEM : CICS region
APPLICATION : CARDPAC/NAS/OLA etc.
COMMENTS :
SMR Number & date fax to SP :
Sample RDO model (For all CICS 4.1 and above)
DEFINE FILE (xxxxxx) GROUP (xxxxxxx) *
DSNAME(SAcc.Laa.xxxxxxx) *
STRINGS(3) RECORDFORMAT(F) *
ADD(NO) BROWSE(YES) DELETE(NO) READ(YES) *
UPDATE(NO) STATUS(ENABLED)
STEP 4 : He approves the package CUAT0001 and obtain approval from the Project
Manager. Member CUAT001 will be treated as a request and this
member will be XCOM to SADC.MCM.JCL.CUAT.BASE0 upon approval by the
creator and the Project Manager.
2. Upon receiving the SMR, CICS SP checks out the CICS table/RDO from CHANGEMAN
managed UAT or Production source library. He incorporates necessary amendment in the
CICS table request base on the information provided by the programmer in the Request
PDS. If there are any other special requirement, he then documents the same in the
October 15, 1997 61

COMMENTS column.
3. Upon completion, CICS SP stage in the CICS changes through CHANGEMAN.
4. CICS SP runs Audit to ensure no out-of-sync situation occurs.
5. CICS SP freezes the change package.
6. CICS SP obtains approval from the peer reviewer, auditor, data center manager and then
pass on to librarian. (different approval levels for different types of request)
7. The librarian runs comparison report for CICS SP and his peer reviewer for examination.
8. Librarian obtains signature from the data center manager and does the final approval.
CHANGEMAN ripple the baseline library and update the base library with the latest
UAT/Production source and load version automatically for macro changes. For RDO a
job is triggered to production, to update the CICS CSD.
9. Upon completion, CICS SP will move the member from SADC.MCM.JCL.xxxx.BASE0 to
STDC.MDC.CICS.xxxx.REQUEST.DONE.
10. CICS SP will check the request daily. The SLA are as follows.
a) TEST changes 2 days (upon receipt of complete management signoff SMR)
b) UAT changes 3 days (upon receipt of complete management signoff SMR)
c) PROD changes 3 days (upon receipt of complete management signoff SMR)
11. Network changes (e.g., special TCTs, LU6.2 links) project manager will coordinate all
network request through memo to network SP and a copy to CICS SP.
12. New CICS regions has to have approval from Leong Soon Peng / James Berti, and
application team must raise an SMR complete signoff by requester’s management and
counter signoff from Leong Soon Peng / James Berti. Upon receipt of the request and
the SMR, the SLA are as follows:
a) 7 days for RACF and CICS setup
6.2.7. Emergency Update Procedure

Obtain relevant approvals from requester’s management and APCC management.
6.3. CICS Default Users

CICS Version 4.1 and above uses a CICS default user id for each region. The main CICS region default
user id will have eight characters, its related regions will have seven characters. The following documents
the CICS default user id naming convention.
6.3.1. Cardpac Application Regions
eccUSRSn where e denotes Environment

e = T for Test Environment
e = E for Training Environment
e = A for UAT Environment
e = P for Production Environment
where cc denotes Country Code or Data-center
e.g., cc = SG for Singapore
where S for Cardpac regions
n = 1 to 9 numeric for mirror regions in CICSPLEX environment
E.g. of a cardpac application Region default user id
TINUSRS1 Indonesia cardpac default userid for TINCICS1

TINUSRR1 Indonesia country TOR with applid TINCICR1
October 15, 1997 62

6.3.2. Systematic Application Regions
eccUSRli where e denotes Environment

e = E for Training Environment
where cc denotes Country Code
e.g., cc = SB for Samba
where I for Banking regions
E.g. of a Banking application Region default user id
TPHUSRI1 Phillippines Banking default userid for TPHCICI1
6.4. CICS Preset Userid(s)

CICS Version 4.1 and above uses a CICS preset user-id(s) for terminals that have no signon. The CICS
preset userid(s) will have a max of eight characters. The following documents the CICS preset userid
naming convention.
6.4.1. Cardpac and Banking Application Regions
eccPSUsn where e denotes Environment

where cc denotes Country Code or Data-center
e.g., cc = SG for Singapore
where s denotes types of CICS region

s = S related to Card application regions
s = I related to Banking application regions
s = R related to TORs
E.g. of a Cardpac application Region Preset userid
THKPSUS1 Hong Kong Card preset userid for THKCICS1

TPHPSUI1 Philippines Banking preset userid for TPHCICI1
TPHPSUR1 Philippines Sabre TOR preset userid for TPHCICR1
October 15, 1997 63

6.5. CICS Source, Copy Books, Loadlibs and Changeman Packages

TEST UAT PROD
Version 4
Macro STDC.MCI.LOD SADC.MCM.LOD.ACIC.BASE0 SPSY.MCI.LOD
Source STDC.MCI.SRC.V410 SADC.MCM.SRC.ACIC.BASE0 SADC.MCM.SRC.PCIC.BASE0
Cpy STDC.MCI.CPY SADC.MCM.CPY.ACIC.BASE0 SADC.MCM.CPY.PCIC.BASE0
Packid --NA-- ACIC PCIC
SIT SASY.MCM.LOD.R410.BASE0 SASY.MCM.LOD.A410.BASE0SPSY.MCI.LOD.SIT410

Source SADC.MCM.SRC.R410.BASE0 SADC.MCM.SRC.A410.BASE0 SADC.MCM.SRC.P410.BASE0
Packid R410 A410 P410
RDO Country CSD Country CSD Country CSD

Source STDC.MCI.SRC.RDO(sample) SADC.MCM.JCL.ARDR.BASE0 SADC.MCM.JCL.PRDR.BASE0
Packid --NA-- ARDR PRDR
Version 5
Macro STDC.MCI.LOD.R530 SADC.MCM.LOD.AC53.BASE0 SPSY.MCI.LOD.R530
Source STDC.MCI.SRC.V530 SADC.MCM.SRC.AC53.BASE0 SADC.MCM.SRC.PC53.BASE0
Cpy STDC.MCI.CPY SADC.MCM.CPY.ACIC.BASE0 SADC.MCM.CPY.PC53.BASE0
Packid --NA-- AC53 PC53
SIT SADC.MCM.LOD.R530.BASE0 SADC.MCM.LOD.A530.BASE0 SPSY.MCI.LOD.SIT530

Source SADC.MCM.SRC.R530.BASE0 SADC.MCM.SRC.A530.BASE0 SADC.MCM.SRC.P530.BASE0
Packid R530 A530 P530
RDO Country CSD Country CSD Country CSD

Source STDC.MCI.SRC.RDO(sample) SADC.MCM.JCL.ARDR.BASE0 SADC.MCM.JCL.PRDR.BASE0
Packid --NA-- ARDR PRDR
6.6. CICS Startup deck (JCL) for all CICS Version and Changeman Packages
TEST UAT PROD
JCL SASY.MSY.PRC SASY.MSY.PRC SPSY.MSY.PRC

Packid ASYS ASYS PSYS
6.7. CICS Source, Loadlibs and Changeman Packages
For DB2 RCTs , CICS Exits and customized programs
TEST UAT PROD

Version 4
DB2 RCTs
Lod SASY.MCM.LOD.R410.BASE0 SASY.MCM.LOD.U410.BASE0 SPSY.MCI.LOD.SIT410
Source SADC.MCM.SRC.R410.BASE0 SADC.MCM.SRC.U410.BASE0 SADC.MCM.SRC.P410.BASE0
Packid RCIC UCIC SCIC
EXITS STDC.MCI.LOD SADC.MCM.LOD.AE41.BASE0 SPSY.MCI.LOD.PE41

Source STDC.MCI.SRC.V410 SADC.MCM.SRC.AE41.BASE0 SADC.MCM.SRC.PE41.BASE0
Cpy STDC.MCI.CPY SADC.MCM.CPY.AE41.BASE0 SADC.MCM.CPY.PE41.BASE0
Packid --NA-- AE41 PE41
Version 5
DB2 RCTs
Lod SASY.MCM.LOD.R410.BASE0 SASY.MCM.LOD.U410.BASE0 SPSY.MCI.LOD.SIT410
Source SADC.MCM.SRC.R410.BASE0 SADC.MCM.SRC.U410.BASE0 SADC.MCM.SRC.P410.BASE0
Packid RCIC UCIC SCIC
October 15, 1997 64

EXITS STDC.MCI.LOD.R530 SADC.MCM.LOD.AE53.BASE0 SPSY.MCI.LOD.PE53

Source STDC.MCI.SRC.V530 SADC.MCM.SRC.AE53.BASE0 SADC.MCM.SRC.PE53.BASE0
Cpy STDC.MCI.CPY SADC.MCM.CPY.AE53.BASE0 SADC.MCM.CPY.PE53.BASE0
Packid --NA-- AE53 PE53
6.8. CICS Naming Convention

In APPC, there are three groupings of CICS Regions as listed in A to C
A. Country Base CICS Regions (AORs)
B. Country Base TOR
C. Common Cards TOR
Within these groupings, there are five environmental set-up as listed in a to e

a. Test - In development
b. TRN - Education/Training
c. UAT - User Acceptance Test
d. CONV - Production Conversion
e. PROD - Production
This document also describe the migration/conversion methods used by cards and banking application.
6.8.1. Country Base CICS Regions
The following conventions are adopted ;
CICS Region Name : xccCICsn

where x denotes T for Test
E for TRN
A for UAT
P for Production
cc denotes country code
where s denotes S for Cards application

I for Banking (Systemmatics) application
B for Banking (Inhouse) application
K for Banking (Night) application
R for TOR regions
where n = 1 to 9 numeric for mirror regions in CICSPLEX

environment
CICS Region datasets : Sxcc.LCI.sn.cics datasets

E for TRN
A for UAT
P for Production
where sn denotes S1 to S9 for cards application

I1 to I9 for banking application
B1 to B9 for Inhouse banking application
K1 to K9 for Night Banking application
R1 to R9 for TOR regions
CICS Application datasets: Sxcc.Laa.**

E for TRN
A for UAT
P for Production
aa denotes application code
October 15, 1997 65

6.8.2. TOR Country Base CICS Regions
For Country Base TORs, it is set-up for Sabre Platform (LU6.2)

application, needing a TOR to route to Bank or cards
application.
The following conventions are adopted :
CICS Region Name : xccCICRn
E for TRN
A for UAT
P for Production
where Rn = R1 to R9
CICS Region datasets : Sxcc.LCI.Rn.cics datasets

E for TRN
A for UAT
P for Production
where Rn = R1 to R9
6.8.3. TOR Common Cards CICS Regions
There is one common TOR set-up for all country cards application. This is for a limited set of card
functions to be accessible from this common TOR.
The following conventions are adopted :
CICS Region Name : xDCCICT1 or xDCCICR1

E for TRN
A for UAT
P for Production
DC denotes Data Center
CICS Region datasets : Sxcc.LCI.Tn.cics datasets or

Sxcc.LCI.Rn.cics datasets
A for UAT
P for Production
6.8.5. Migration / Conversion of Cards Applications
Existing production country to be migrated to a new CICS or application release. If there is

ongoing development for existing application, the current set of CICSes will be retained, and a
new set of CICSes will be set-up with the following convention;
October 15, 1997 66

Current New
- TEST TccCICS TccCIC1 or TccCIC2

- TRN EccCICS EccCIC1 or EccCIC2
- UAT AccCICS AccCIC1 or AccCIC2
- CONV PccCIC1
- PROD PccCICS (On cutover day, PccCIC1 will be renamed to PccCICS)
6.8.5.1.Dataset Naming Convention for the CONV / PRODUCTION CICS

CICS Region Datasets : SPcc.LCI.ss.cics datasets
where cc denotes country code
ss denotes STD new CICS region
STD1 CONV/Prod region
Take note that the CONV regions will have the same naming convention as the
production CICS as these CICS datasets will not be renamed during cutover.
CICS Region Datasets : SPcc.Laa.*.STD

SPcc.Laa.*.ECS

The CONV CICS will be shutdown a few days after the line tests (using the CONV
application datasets). The CICS SP will then rename all the CONV application datasets
to actual production datasets (without the .STD or .ECS). Also the CONV CICS applid
will be rename to the actual production CICS region on the cutover day.
6.9. Migration / Conversion of Banking Applications
Existing production country to be migrated to a new CICS or application release. If there is an ongoing
development for existing application, the current set of CICSes will be retained, and a new set of CICSes
will be set-up with the following convention;
Current New
- TEST TccCICI TccCICJ

- TRN EccCICI EccCICJ
- UAT AccCICI AccCICJ
- CONV PccCICJ
- PROD PccCICI (On cutover day, PccCICC will be renamed to PccCICI)
6.9.1. Dataset Naming Convention for the CONV/PRODUCTION CICS
CICS Region Datasets : SPcc.LCI.ss.cics datasets

ss denotes I new CICS region
I1 CONV/Prod region
Take note that the CONV regions will have the same naming convention as the production CICS
as these CICS datasets will not be renamed during cutover.
CICS Application Datasets : SPcc.Laa.*

SPcc.Laa.*

The CONV CICS will run in parallel with the production CICS for a period of 2 to 3 weeks
depending on application requirement.
October 15, 1997 67

On request from application, a time will be set to rename the CONV application datasets to actual
production datasets, and the CICS applid will be rename to the production applid.
6.10. CICS Version 3.3 Resource Definition On-line (RDO)
In CICS Version 3.3, all FCT,PPT and PCT definitions has been migrated from CICS macros to RDO. All
RDO definitions are modified or updated by a Changeman package in RND LPAR, and the package is
XCOM to production for execution.
6.10.1. To Apply Changes For RDO
The Changeman package ids are;
ARDR - UAT RDO updates to the CSD

ARDI - UAT RDO install (for immediate install of new resources)
PRDR - Production RDO updates to the CSD
PRDI - Production RDO install (for immediate install of new resources)
6.10.2. RDO Definitions & Jobs - Sample Skeleton
The sample skeleton RDO definitions is kept in a dataset in RND LPAR STDC.MCI.SRC.RDO.
Each member is also documented.
Member $INDEX - describes the each member in the dataset

$LSTNAME - describes the naming convention for the LISTNAME in the CSD
$GRPNAME - describes the naming convention for the GROUPNAME in the CSD
DFHCSDUP - sample JCL to update the CSD
CSDLIST - sample JCL to list the CSD
The Production CSD for each country is backed up daily to tape. A hardcopy of the CSD LIST is
kept in production on DASD, e.g. SPxx.LCI.DFHCSD.LIST (where xx denotes country code). This
LIST is deleted and recreated after each update to the CSD.
October 15, 1997 68

6.10.3.STDC.MCI.SRC.RDO
NAME VV.MM CREATED CHANGED SIZE INIT MOD ID
$GROUP 01.03 94/11/10 95/03/23 16:38 13 7 6 OPCHAI1
$GRPNAME 01.04 95/03/23 95/04/28 15:46 55 40 54 OPCHAI1
$INDEX 01.07 95/03/23 95/04/18 17:27 69 13 68 CHAIYPE
$LSTNAME 01.01 95/03/23 95/03/23 17:47 24 40 22 OPCHAI1
ASIACAT 01.00 95/05/14 95/05/14 10:48 84 84 0 OPCHAI1
CSDLIST 01.01 95/05/03 95/06/06 09:11 7 7 0 CHAIYPE
DFHCSDUP 01.01 95/03/23 95/03/23 18:42 22 34 0 OPCHAI1
INPUT 01.00 95/03/24 95/03/24 09:30 7 7 0 CHAIYPE
LU2000NL 01.01 95/05/31 95/05/31 09:53 30 30 0 OPCHAI1
MIGRATE 01.47 93/09/06 95/05/03 10:53 66 15 0 OPCHAI1
PICCTCT 01.00 95/05/02 95/05/02 09:36 80 80 0 CHAIYPE
RDADAPPC 01.00 95/03/30 95/03/30 16:48 30 30 0 CHAIYPE
RDADCAST 01.02 95/05/02 95/05/03 16:50 38 88 0 OPCHAI1
RDADDEDC 01.04 95/05/03 95/05/16 17:31 304 275 0 OPCHAI1
RDADDFCT 01.05 95/03/23 95/03/24 09:54 56 22 0 CHAIYPE
RDADDMRO 01.00 95/03/30 95/03/30 15:52 20 20 0 CHAIYPE
RDADDPCT 01.02 95/03/23 95/03/24 09:31 41 13 0 CHAIYPE
RDADDPPT 01.01 95/03/23 95/03/24 09:54 39 12 0 CHAIYPE
RDADDTCT 01.01 95/04/28 95/04/28 16:05 43 41 0 OPCHAI1
RDADDVRU 01.01 95/05/02 95/05/02 11:42 26 43 0 OPCHAI1
RDADICC 01.02 95/05/03 95/05/03 17:01 78 38 0 OPCHAI1
RDADMAST 01.05 95/05/02 95/06/16 16:39 72 113 0 CHAIYPE
RDADVISA 01.04 95/03/28 95/06/08 18:25 60 73 0 CHAIYPE
RDALTFCT 01.01 95/03/24 95/04/28 16:11 50 50 0 OPCHAI1
RDALTPCT 01.02 95/03/24 95/04/28 16:11 49 50 0 OPCHAI1
RDALTPPT 01.02 95/04/28 95/04/28 16:11 39 49 0 OPCHAI1
RDALTTCT 01.01 95/04/28 95/04/28 16:10 19 43 0 OPCHAI1
RDDELFCT 01.00 95/03/24 95/03/24 10:53 37 37 0 CHAIYPE
RDDELPCT 01.00 95/03/24 95/03/24 10:51 36 36 0 CHAIYPE
RDDELPPT 01.01 95/03/24 95/03/24 10:49 37 39 0 CHAIYPE
RDDELTCT 01.01 95/04/28 95/04/28 16:15 28 43 0 OPCHAI1
TDCCITA3 01.99 93/07/23 95/05/03 10:51 43 3 0 OPCHAI1
TDCCI33R 01.02 94/12/26 95/03/23 18:09 61 61 0 OPCHAI1
TLU2EDC 01.02 95/05/03 95/05/03 16:42 30 30 0 OPCHAI1
TLU2VISA 01.01 95/06/08 95/06/08 18:27 57 56 0 CHAIYPE
TLU2VRU 01.01 95/04/28 95/05/03 16:42 29 29 0 OPCHAI1
TLU2000 01.02 95/04/28 95/05/03 16:43 30 30 0 OPCHAI1
TLU2000N 01.04 95/03/28 95/05/03 16:43 56 29 0 OPCHAI1
TLU3000 01.02 95/05/02 95/05/03 16:43 30 30 0 OPCHAI1
TLU3000E 01.03 95/04/28 95/05/03 16:43 30 30 0 OPCHAI1
TLU3000H 01.05 95/04/25 95/05/03 16:44 30 28 0 OPCHAI1
TYPETERM 01.00 95/04/28 95/04/28 16:58 26 26 0 OPCHAI1
TYP3767C 01.03 95/03/31 95/05/03 16:44 28 80 0 OPCHAI1
TYP3790 01.01 95/05/02 95/05/03 16:44 30 30 0 OPCHAI1
October 15, 1997 69

6.10.4.STDC.MCI.SRC.RDO ($INDEX)
********************************* TOP OF DATA **************************

*
* THIS DATASET CONTAINS MEMBERS(JOBS) USED FOR RDO UPDATES IN CICS.
* A BRIEF DESCRIPTION IS SETUP FOR EACH MEMBER.
**********************************************************************
NAMING CONVENTION FOR THE MEMBERS :
RDXXXPPT WHERE XXX DENOTES ADD - TO ADD PPT
DEL - TO DELETE PPT
ALT - TO ALTER PPT
RDXXXPCT WHERE XXX DENOTES ADD - TO ADD PCT
DEL - TO DELETE PCT
ALT - TO ALTER PCT
RDXXXFCT WHERE XXX DENOTES ADD - TO ADD FCT
DEL - TO DELETE FCT
ALT - TO ALTER FCT
RDXXXTCT WHERE XXX DENOTES ADD - TO ADD TCT
DEL - TO DELETE TCT
ALT - TO ALTER TCT
RDXXXTYP WHERE XXX DENOTES ADD - TO ADD TYPETERM
DEL - TO DELETE TYPETERM
ALT - TO ALTER TYPETERM
RDXXXMRO WHERE XXX DENOTES ADD - TO ADD MRO
DEL - TO DELETE MRO
ALT - TO ALTER MRO
RDXXXISC WHERE XXX DENOTES ADD - TO ADD ISC
DEL - TO DELETE ISC
ALT - TO ALTER ISC
RDXXXLST WHERE XXX DENOTES APP - TO APPEND (CREATE) LIST
RDPRTXXX WHERE XXX DENOTES LST - TO PRINT CSD LIST
PPT - TO PRINT PROGRAMS
PCT - TO PRINT TRANSACTIONS
FCT - TO PRINT FILES
TCT - TO PRINT TERMINALS
RDXXXGRP WHERE XXX DENOTES ADD - TO ADD GROUPS TO LIST
REM - TO REMOVE GROUPS FROM LIST
CPY - TO COPY GROUPS
TYXXXXXX WHERE XXXXXX DENOTES LU2000 - FOR TYPETERM LUTYPE2
E.G. NORMAL TERMINALS
LU3000 - FOR TYPETERM LUTYPE3
E.G. PRINTERS
LU2VRU - FOR TYPETERM VRUS
TYP3790 3790 - FOR TYPETERM 3790000
E.G. NCR MIP
E.G. LECAST TERMINALS
TYPCONSL CONSL - FOR TYPETERM CONSL001
E.G. CONSOLES
TLU2000N LU2000N - FOR TYPETERM LUTYPE2 WITHOUT
UPPERCASE CHARACTER TRANSLATION
TLU3000E LU3000E - FOR TYPETERM LUTYPE3
WITH PRINTING COLUMNS OF 133 CHARACTERS
TDCCITA3 - THIS JOB IS USED TO COMPILE THE CICS MACRO
FOR MIGRATION PURPOSES
TDCCI33R - COMPILING PROCEDURE USE TO COMPILE THE
CICS MACRO FOR MIGRATION PURPOSES.
THE LOAD WILL BE KEPT IN
STDC.MCI.LOD.RDO
MIGRATE - TO MIGRATE THE CICS MACRO FROM LOADS TO RDO

FORMAT FOR MIGRATION PURPOSES.
6.10.5.STDC.MCI.SRC.RDO ($LSTNAME)
****************************************** TOP OF DATA ***********************************
October 15, 1997 70

*
* A BRIEF DESCRIPTION IS SETUP FOR THE RDO LIST NAMING CONVENTIONS
*
1). THE CICS RESOURCE DEFINITION ON-LINE IS KEPT IN A VSAM DATASET
WITH THE FOLLOWING CONVENTION :
SPXX.LCI.STD.DFHCSD WHERE XX DENOTES COUNTRY CODE
SN FOR SINGAPORE (ECS APPLICATION)
WA FOR WEST ASIA (ECS APPLICATION)
SPSG.LCI.A.DFHCSD WHERE A DENOTES SYSTEMATIC DAY CICS
SPSG.LCI.K.DFHCSD WHERE K DENOTES SYSTEMATIC NIGHT CICS
2). EACH CSD HAS AN ACTIVE LIST WITH THE FOLLOWING NAMING CONVENTION :
PXXLIST WHERE XX DENOTES COUNTRY CODE
SN FOR SINGAPORE (ECS APPLICATION)
WA FOR WEST ASIA (ECS APPLICATION)
SI FOR SINGAPORE (DAY SYSTEMATIC)
SK FOR SINGAPORE (NIGHT SYSTEMATIC)
3). EACH CSD IS BACKUP EVERY NIGHT AFTER BATCH RUNS BY
OPERATIONS
USING DFDSS BACKING UP WITH PREFIX OF SPXX.LCI.**
6.10.6. STDC.MCI.SRC.RDO ($GRPNAME)
********************************* TOP OF DATA ***********************************************

* *
* A BRIEF DESCRIPTION IS SETUP FOR THE GROUPS NAMING CONVENTIONS *
**************************************************************************************************
1). EACH CSD HAS AN ACTIVE LIST WHICH CONTAINS GROUPS WHICH WILL BE
INSTALLED DURING A COLD START
2). THE GROUPS NAMING CONVENTIONS ARE :
FOR ECS APPLICATION

PCCXXPPT WHERE XX DENOTES CC DENOTES
(PROGRAMS) CP FOR CARDPAC SN - SINGAPORE
OA FOR OLA WA - WEST ASIA
CA FOR CACS
NA FOR NAS
RS FOR RMS
SS FOR CARDPAC SECURITY
PCCXXPCT WHERE XX DENOTES CC DENOTES

(TRANSACTIONS)CP FOR CARDPAC SN - SINGAPORE
OA FOR OLA WA - WEST ASIA
CA FOR CACS
NA FOR NAS
RS FOR RMS
PCCXXFCT WHERE XX DENOTES CC DENOTES

(FILES) CP FOR CARDPAC SN - SINGAPORE
OA FOR OLA AE - WEST ASIA
CA FOR CACS PK - PAKISTAN
NA FOR NAS
RS FOR RMS
FOR SYSTEMATIC APPLICATION
PXXGCPPT WHERE XX DENOTES

(PROGRAMS) SI FOR DAY CICS
SK FOR NIGHT CICS
PXXGCPCT WHERE XX DENOTES

(TRANSACTIONS) SI FOR DAY CICS
SK FOR NIGHT CICS
PXXGCFCT WHERE XX DENOTES

(FILES) SI FOR DAY CICS
SK FOR NIGHT CICS
October 15, 1997 71

FOR PRODUCTION TERMINAL GROUPS
PXXLLTCT XX DENOTES COUNTRY

LL DENOTES LINE NUMBER
6.10.7. STDC.MCI.SRC.RDO (DFHCSDUP)
********************************* TOP OF DATA ****************************************

//TDCCYPE JOB (#0000),'CSDADDE',CLASS=I,MSGCLASS=X,
// MSGLEVEL=(1,1),NOTIFY=SUNDARR
//*
//MIG EXEC PGM=DFHCSDUP,REGION=1024K,PARM='COMPAT'
//*-------------------------------------------------------------------------------------------------------
//*
//* JOB TO UPDATE CSD , ADD SYSIN DD
//* FOLLOW SAMPLE SKELETON FROM RDXXXPPT
//* RDXXXPCT
//* RDXXXFCT
//* ETC...
//*
//*-------------------------------------------------------------------------------------------------------
//STEPLIB DD DSN=CICS330.SDFHLOAD,DISP=SHR
// DD DSN=STDC.MCI.LOD,DISP=SHR
//DFHCSD DD DSN=STWA.LCI.DFHCSD,DISP=SHR <=== CSD NAME
//INCSD DD DSN=STWA.LCI.STD.DFHCSD,DISP=SHR <=== INPUT CSD
//SYSIN DD *
*
* COPY SAMPLE SKELETON FROM RDXXX MEMBERS
6.10.8. STDC.MCI.SRC.RDO (RDADVISA)
//*------------------------------------------------------------------
//* SOURCE FOR RDO UPDATES
//* FUNCTION : TO ADD NEW VISA TERMINALS
//* GROUP : CHOOSE GROUPS
//* TCTVISA - FOR TEST
//* PTCTVISA - FOR PRODUCTION VISA
//* or use TCT group naming convention
//*
//* INPUT : 1). ADD AFTER SYSIN DD IN JOBS depending on environments
//* Test : STDC.MCI.SRC.RDO(DFHCSDUP)
//* UAT : Changeman Package Id (ARDR)
//* PROD : Changeman Package Id (PRDR)
//* 2). Repeat DEFINE statements for additional terminals
//* 3). Any additional parameters needed , refer to CICS
//* RDO Guide V3.3 SC33-0666-02
//*
//* NOTES : This is for defining VISA terminals.
//*
//* - Enter TERMINAL ( 4 character )
//* - Enter NETNAME ( 8 character )
//* - Enter GROUPNAME
//*
//* It is a pair of terminals,
//* One terminal to read with transaction OAVA
//* One terminal to write with transaction OAWA
//*
//* Check transaction with application team.
//*------------------------------------------------------------------------------------------------------
DEF TERMINAL(XXXX) GROUP(XXXXXXXX) AUTINSTMODEL(NO)
TYPETERM(LU2VISA) NETNAME(XXXXXXXX) CONSOLE(NO)
PRINTERCOPY(NO)
ALTPRINTCOPY(NO)
TASKLIMIT(NO)
OPERPRIORITY(0) OPERRSL(0)
OPERSECURITY(1)
TRANSACTION(OAVA) TERMPRIORITY(250) INSERVICE(YES)
ATTACHSEC(LOCAL)
BINDSECURITY(NO)
DEF TERMINAL(XXXX) GROUP(XXXXXXXX) AUTINSTMODEL(NO)

October 15, 1997 72

PRINTERCOPY(NO)
ALTPRINTCOPY(NO)
TASKLIMIT(NO)
OPERSECURITY(1)
TRANSACTION(OAWA) TERMPRIORITY(250) INSERVICE(YES)
ATTACHSEC(LOCAL)
BINDSECURITY(NO)
DEF TERMINAL(C820) GROUP(VISATCT) AUTINSTMODEL(NO)

PRINTERCOPY(NO)
ALTPRINTCOPY(NO)
TASKLIMIT(NO)
OPERSECURITY(1)
TRANSACTION(OAVA) TERMPRIORITY(250) INSERVICE(YES)
ATTACHSEC(LOCAL)
BINDSECURITY(NO)
6.10.9. STDC.MCI.SRC.RDO (TLU2VISA)
********************************* TOP OF DATA **************************

//*------------------------------------------------------------------
//* FUNCTION : TO ADD NEW TYPETERMS
//* usually typeterms defined to relevant terminal groups
//* ===> SEE NOTES BELOW
//*
//* RDO Guide V3.3 SC33-0666-02
//*
//* NOTES : THIS IS FOR DEFINING TYPETERM(LU2visa), TYPETERMS
//* FOR LUTYPE2 TERMINALS WITHOUT CHARACTER TRANSLATION
//* and used for visa terminals
//*
//* CHOOSE GROUP NAME, CAN BE DEFINED TOGETHER IN ANY
//* TERMINAL GROUP.
//*
//* NOT ADVISABLE TO HAVE DUPLICATE TYPETERM IN A LIST,
//* AS CONFUSION MAY ARISE AS WHICH TYPETERM IT USES.
//* BUT IF DUPLICATE EXIST, THE TYPETERM WITHIN THE GROUP
//* IS TAKEN OR THE TYPETERM ...............
//*--------------------------------------------------------------------------------------------------------------
*
DEF TYPETERM(LU2VISA) GROUP(APCCTYPE)
DEVICE(LUTYPE2) TERMMODEL(2)
SHIPPABLE(NO)
PAGESIZE(24,80) ALTPAGE(24,80) ALTSUFFIX(4)
FMHPARM(NO) OBOPERID(NO)
AUTOPAGE(NO)
DEFSCREEN(24,80) ALTSCREEN(24,80) APLKYBD(NO)
APLTEXT(NO) AUDIBLEALARM(NO) COLOR(NO)
COPY(NO) DUALCASEKYBD(YES) EXTENDEDDS(NO)
HILIGHT(NO) KATAKANA(NO) LIGHTPEN(NO)
MSRCONTROL(NO) OBFORMAT(NO) PARTITIONS(NO)
PRINTADAPTER(NO) PROGSYMBOLS(NO) VALIDATION(NO)
FORMFEED(NO) HORIZFORM(NO) VERTICALFORM(NO)
TEXTKYBD(NO) TEXTPRINT(NO) QUERY(NO)
OUTLINE(NO) SOSI(NO) BACKTRANS(NO)
CGCSGID(0,0)
ASCII(NO) SENDSIZE(1536) RECEIVESIZE(256)
BRACKET(YES)
ERRLASTLINE(YES) ERRINTENSIFY(YES) ERRCOLOR(NO)
ERRHILIGHT(BLINK)
AUTOCONNECT(NO) ATI(YES) TTI(YES)
CREATESESS(YES) RELREQ(NO) DISCREQ(YES)
October 15, 1997 73

NEPCLASS(0) SIGNOFF(LOGOFF) XRFSIGNOFF(NOFORCE)

ROUTEDMSGS(ALL) LOGONMSG(YES)
BUILDCHAIN(YES) USERAREALEN(0) IOAREALEN(3000,4000)
UCTRAN(NO)
RECOVOPTION(SYSDEFAULT)
RECOVNOTIFY(NONE)
6.10.10.STDC.MCI.SRC.RDO (TLU2000N)
//*-----------------------------------------------------------------------------------------------------
//* FUNCTION : TO ADD NEW TYPETERMS
//* usually typeterms defined to relevant terminal groups
//* ===> SEE NOTES BELOW
//*
//* RDO Guide V3.3 SC33-0666-02
//*
//* NOTES : THIS IS FOR DEFINING TYPETERM(LU2000N), TYPETERMS
//* FOR LUTYPE2 TERMINALS WITHOUT CHARACTER TRANSLATION
//*
//* CHOOSE GROUP NAME, CAN BE DEFINED TOGETHER IN ANY
//* TERMINAL GROUP.
//*
//* NOT ADVISABLE TO HAVE DUPLICATE TYPETERM IN A LIST,
//* AS CONFUSION MAY ARISE AS WHICH TYPETERM IT USES.
//* BUT IF DUPLICATE EXIST, THE TYPETERM WITHIN THE GROUP
//* IS TAKEN OR THE TYPETERM ...............
//*-----------------------------------------------------------------------------------------------------------
*
DEF TYPETERM(LU2000N) GROUP(APCCTYPE)
DEVICE(LUTYPE2) TERMMODEL(2)
SHIPPABLE(NO)
PAGESIZE(24,80) ALTPAGE(24,80) ALTSUFFIX(4)
FMHPARM(NO) OBOPERID(NO)
AUTOPAGE(NO)
DEFSCREEN(24,80) ALTSCREEN(24,80) APLKYBD(NO)
APLTEXT(NO) AUDIBLEALARM(NO) COLOR(NO)
COPY(NO) DUALCASEKYBD(YES) EXTENDEDDS(NO)
HILIGHT(NO) KATAKANA(NO) LIGHTPEN(NO)
MSRCONTROL(NO) OBFORMAT(NO) PARTITIONS(NO)
PRINTADAPTER(NO) PROGSYMBOLS(NO) VALIDATION(NO)
FORMFEED(NO) HORIZFORM(NO) VERTICALFORM(NO)
TEXTKYBD(NO) TEXTPRINT(NO) QUERY(NO)
OUTLINE(NO) SOSI(NO) BACKTRANS(NO)
CGCSGID(0,0)
ASCII(NO) SENDSIZE(1536) RECEIVESIZE(256)
BRACKET(YES)
ERRLASTLINE(YES) ERRINTENSIFY(YES) ERRCOLOR(NO)
ERRHILIGHT(BLINK)
AUTOCONNECT(NO) ATI(YES) TTI(YES)
CREATESESS(YES) RELREQ(NO) DISCREQ(YES)
NEPCLASS(0) SIGNOFF(LOGOFF) XRFSIGNOFF(NOFORCE)
ROUTEDMSGS(ALL) LOGONMSG(YES)
BUILDCHAIN(YES) USERAREALEN(0) IOAREALEN(3000,4000)
UCTRAN(NO)
RECOVOPTION(SYSDEFAULT)
RECOVNOTIFY(NONE)
6.10.11.STDC.MCI.SRC.RDO (CSDLIST)
//TDCCYP1 JOB (NUMBER),'MIGRATE’,CLASS=I,MSGCLASS=X,NOTIFY=SUNDARR

//MIG EXEC PGM=DFHCSDUP,REGION=1024K,PARM='COMPAT'
//STEPLIB DD DSN=CICS330.SDFHLOAD,DISP=SHR
//DFHCSD DD DSN=STTU.LCI.A.DFHCSD,DISP=SHR
//SYSIN DD *
LIST G(TCT69) OBJECTS
******************************** BOTTOM OF DATA *********************
October 15, 1997 74

6.10.12.TEST, SIT, UAT CICS Regions in ‘g’ RND LPAR (Telepark)
6.10.12.1. ICBS Group

TEST SIT UAT VER APPLICATION
TPHCICT 3.3.0 Philippines ICBS Training
TGMCICI AGMCICI 3.3.0 Guam ICBS Systematics
TGMCICT 3.3.0 Guam ICBS Systematics Training
TTUCICI ATUCICI 3.3.0 Turkey ICBS Systematics + DB2
ATUCICN 3.3.0 Turkey ICBS Systematics (Nite)
TICCICE 4.1.0 ICBS Systematics Training
TPHCICI SPHCICI APHCICI 4.1.0 Phil ICBS Systematics
TPHCICR SPHCICR APHCICR 4.1.0 Phil ( Sabre TOR )
TDCCICR ADCCICR 4.1.0 Turkey TOR Cards
TINCICI SINCICI AINCICI 4.1.0 Indonesia ICBS Systematics
TINCICR SINCICR AINCICR 4.1.0 Indonesia ( Sabre TOR )
TTWCICI STWCICI ATWCICI 4.1.0 Taiwan ICBS Systematics
TTWCICR STWCICR ATWCICR 4.1.0 Taiwan ( Sabre TOR )
TAECICI SAECICI AAECICI 4.1.0 UAE ICBS Systematics
TAECICR SAECICR AAECICR 4.1.0 UAE ( Sabre TOR )
TPKCICI SPKCICI APKCICI 4.1.0 Pakistan ICBS Systematics
TPKCICR SPKCICIR APKCICR 4.1.0 Pakistan ( Sabre TOR )
TOZCICI AOZCICI 4.1.0 Australia ICBS Systematics
TOZCICA 4.1.0 Australia ICBS Systematics
TOZCICR AOZCICR 4.1.0 Australia ( Sabre TOR )
TPLCICI SPLCICI APLCICI 4.1.0 Poland ICBS Systematics
TPLCICR SPLCICR APLCICR 4.1.0 Poland ( Sabre TOR )
TTHCICI ATHCICI 4.1.0 Thailand ICBS Systematics
TTHCICR STHCICR ATHCICR 4.1.0 Thailand ( Sabre TOR )
TNZCICI SNZCICI ANZCICI 4.1.0 New Zealand ICBS Systematics
TNZCICR SNZCICR ANZCICR 4.1.0 New Zealand (Sabre TOR)
TRBCISI SRBCISI 4.1.0 Regional Base Systematics
TRBCRSI SRBCRSI 4.1.0 Reg. Base System (Sabre TOR)
TRBCISF 4.1.0 Regional Base - Share Finance
TRBCIUW 4.1.0 Reg. Base - Universal Workstation
TRBCRUW 4.1.0 Reg. Base - Universal Wrkst(TOR)
TRBCIY2 4.1.0 Reg. Base - Year 2000 Systematics
TRBCRY2 4.1.0 Reg. Base - Year 2000 Systematics
TGBCICI AGBCICI 4.1.0 Global Systematics
THKCICI 4.1.0 Hong Kong Systematics
6.10.12.2.RCC Group
TEST UAT VER APPLICATION
TNACICS 3.3.0 Global STD NAS

TTUCICS ATUCICS 4.1.0 Turkey ECS
TTUCICT 4.1.0 Turkey ECS Training
TDCCICE 4.1.0 ECS Training
ARACICS 4.1.0 RACF ROAR system
TPHCIC1 APHCIC1 4.1.0 Philippines ECS
TPHCIC2 4.1.0 Phil ECS (parallel run)
THKCICS AHKCICS 4.1.0 HKG ECS
THKCIC2 4.1.0 HKG (parallel run & conversion)
THKCICE 4.1.0 HKG ECS Training
6.10.13.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)
6.10.13.1.RCC & PBG Group

TSICICT ASICICT 2.1.2 Zurich PBG CICS

TSICIC1 ASICIC1 2.1.2 Zurich PBG CICS
TSICIC2 ASICIC2 2.1.2 Zurich PBG CICS
TSBCICS ASBCICS 3.3.0 Samba ECS
TDCCICT ADCCICT 3.3.0 Common TOR Cross Border CICS
TDCCICS 3.3.0 Systematic Vanilla System
TSGCICA ASGCICI 3.3.0 Systematic + Natural/DB2
TSGCICN ASGCICN 3.3.0 Systematic + Natural (nite)
October 15, 1997 75

ASGCICA 3.3.0 Systematic + Natural/DB2

TSGCICT 3.3.0 Systematic Training
TWACICS AWACICS 3.3.0 West Asia (ECS V1)
TWACIC2 3.3.0 West Asia ECS parallel run
TINCIC1 AINCIC1 3.3.0 Indonesia ECS
TINCIC2 3.3.0 Indonesia ECS parallel run
TINCIC3 AINCIC3 3.3.0 Indonesia NAS upgrade
TSNCICS ASNCICS 3.3.0 Singapore ECS (DB2)
TIDCICS 3.3.0 India Systematics + Natural/DB2
TMLCICA 3.3.0 Malaysia Systematics
TMLCIC1 3.3.0 Malaysia ECS
DMBCICT UMBCICT 4.1.0 PBG OSCAR
DMBCIC1 UMBCIC1 4.1.0 PBG OSCAR
DMBCIC2 UMBCIC2 4.1.0 PBG OSCAR
TJPCICI AJPCICI 4.1.0 Japan Systematics
TJPCICA AJPCICA 4.1.0 Japan Systematics
TJPCICN 4.1.0 Japan Systematics (Nite)
TRCCICS 4.1.0 Regional GCB
TTWCICS ATWCICS 4.1.0 Taiwan ECS
TGBCIC1 4.1.0 Common ECS (DB2)
TTHCIC1 ATHCIC1 4.1.0 Thailand ECS
TTHCIC2 4.1.0 Thailand ECS parallel run
TTWCIC1 ATWCIC1 4.1.0 Taiwan ECS (Diners only)
THKCIC1 AHKCIC1 4.1.0 Hong Kong OLA Diners
TJPCIC1 AJPCIC1 4.1.0 Japan Cards conversion to V4.1
TPKCICS APKCICS 4.1.0 Pakistan ECS
TAECICS AAECICS 4.1.0 UAE ECS
TRCCICS 4.1.0 Regional Citiplus
TRBCIMD 4.1.0 Regional Base - multi curr Deposit
TKRCICS AKRCICS 4.1.0 Korea ECS
TWACICT 4.1.0 West Asia Training
TRPLCICS APLCICS 4.1.0 Poland ECS
October 15, 1997 76

6.10.14.TEST, SIT, UAT CICS Regions in ‘w’ RND LPAR (Telepark)
6.10.14.1.RCC & PBG Group

TJPCIC1 AJPCIC1 4.1.0 Japan Cards conversion to V4.1

TPKCICS APKCICS 4.1.0 Pakistan ECS
TAECICS AAECICS 4.1.0 UAE ECS
TRCCICS 4.1.0 Regional Citiplus
TRBCIMD 4.1.0 Regional Base - multi curr Deposit
TKRCICS 4.1.0 Korea ECS
TWACICT 4.1.0 West Asia Training
TPLCICS 4.1.0 Poland ECS
6.10.15.Production CICS Regions in PROD LPAR
PROD VER APPLICATION
PSICICT 2.1.2 TOR PBG Zurich

PSICIC1 2.1.2 PBG Zurich
PSICIC2 2.1.2 PBG Zurich
PDCCICT 3.3.0 Common Cross Border CICS
PINCICS 3.3.0 Indonesia Cardpac
PSBCICS 3.3.0 Samba Cardpac
PSNCICS 3.3.0 Singapore ECS
PSGCICI 3.3.0 Systematics + Natural
PSGCICK3.3.0 Systematics + Natural for night
PGMCICI 3.3.0 Guam Systematics
PTUCICI 3.3.0 Turkey Systematics
PTUCICK 3.3.0 Turkey Systematics for night
PJPCICS 4.1.0 Japan Cardpac
PTHCICS 4.1.0 Thailand ECS
PPHCICS 4.1.0 Philippines ECS
PPHCICR4.1.0 Philippines ( Sabre TOR )
PPHCICI/J 4.1.0 Philippines Systematics
PTUCICS 4.1.0 Turkey ECS
PTUCICR 4.1.0 Turkey TOR (banks & cards)
PTWCIC1 4.1.0 Taiwan Diners OLA
PHKCICS 4.1.0 Hong Kong ECS
PHKCIC1 4.1.0 Hong Kong OLA
PTWCICS 4.1.0 Taiwan ECS
PAECICS 4.1.0 UAE ECS
PPKCICS 4.1.0 Pakistan ECS
PPLCICIS 4.1.0 Poland ECS
6.10.16.Test CICS Regions in HONG KONG RND LPAR (CINTECH II)
TNCSDINT 2.1.2 Hong Kong Diners

TNCSHOPN 2.1.2 HKG Banking
TNCDNAST 2.1.2 HKG NAS
TNCSPORE 2.1.2 Singapore Cardpac in HKG
TNCSTRAN 2.1.2 HKG Training Region
TNCSTWOL 2.1.2 Taiwan Banking
TNCSUPT 2.1.2 User Participating Test in HKG
TNCSVISA 2.1.2 HKG Visa
TNCSTOR 2.1.2 HKG TOR
TNCSUTOR 2.1.2 HKG TOR
TNCSVTOR 2.1.2 HKG TOR for CICSTRAN
TNCSTOR2 2.1.2 HKG TOR2
TNCDIN3 2.1.2 HKG Diners
THKCICU 2.1.2 HKG ECS
THKCICE 2.1.2 HKG ECS
THKCIC9 2.1.2 HKG Temp Banking CICS
THKCICN 2.1.2 HKG Banking Night CICS
6.10.17.QA CICS in QA LPAR
CICSDCQA 2.1.2 Hong Kong Diners

CICSISQA 2.1.2 Hong Kong Banking
October 15, 1997 77

CICSMAQA 2.1.2 Macau Banking

CICSTWDC 2.1.2 Taiwan Diners/Banking
CICSVCQA 2.1.2 Hong Kong Visa (OLA)
CICSTOR2.1.2 TOR
CICSUTOR 2.1.2 TOR
6.10.18.Production Regions in Hong Kong LPAR
PRODBANK 2.1.2 Hong Kong Banking

PRODMACU 2.1.2 Macau Banking
PRODTAWD 2.1.2 Taiwan Diners
PRODDINR 2.1.2 Hong Kong Diners
PRODUTOR 2.1.2 TOR
PRODTOR 2.1.2 TOR
PRODCPO 2.1.2 Hong Kong Mini Offshore banking
6.10.19.On-Line Only On User Request

PRODDCC 2.1.2 HKG Diners Mini CICS ( for user inquiry )
PRODCVV2 2.1.2 HKG Diners Mini CICS ( for PIN generation)
PRODCVTD 2.1.2 Taiwan Diners Mini CICS ( for user inquiry )
PRODTDCC 2.1.2 Taiwan Diners Mini CICS ( for PIN generation)
6.10.20.Test and UAT CICS Regions in Australia RND LPAR
IRBSTST RBSUAT 2.1.2 Systematics TOR

IRBST2 IRBSA2 2.1.2 Systematics AOR
IRBST3 IRBSA3 2.1.2 Systematics AOR
IRBSTRN 2.1.2 Systematics + Cardpac Training TOR
IRBSR2 2.1.2 Systematics + Cardpac Training AOR
IRBSZCSI 2.1.2 Systematics Conversion TOR
IRBSZ1 2.1.2 Systematics Conversion AOR
IRBSDEV 2.1.2 Systematics Development
IRBSVAN 2.1.2 Systematics Vanilla
IRBSV25 3.3.0 Systematics Vanilla
BCT33 BCU33 3.3.0 Cardpac
BCR33 3.3.0 Cardpac Training AOR
TDCCICA ADCCICA3.30 TOR to Crossborder CICses
6.10.21.Production CICS Regions in AUSTRALIA Production LPAR
IRBSPRD 2.1.2 Systematics TOR

IRBSP1 2.1.2 Systematics AOR
IRBSP2 2.1.2 Systematics AOR
BCR33 3.3.0 Cardpac AOR
PDCCICA 3.3.0 TOR to Crossborder CICses
6.10.22.Update SNT Table in Test, UAT and Production HKG CICS
1) All Test HKG CICS uses the same SNT. The Test HKG CICSes are for VISA, BANK, DINERS, MACAU
and TAIWAN. The SNT is complied by direct update.
Source : TNSPU.CICS.TABLE
Member : THKSNT1
JCL : TNSPU.CICS.TABLE(TABLE)
2) All UAT HKG CICS uses the same SNT. The SNT is compiled using Changeman
packages. The package ids are as follows :
CICS Package Id Source

VISA HA10 AHKSNTQA
BANK “ “
DINERS “ “
October 15, 1997 78

MACAU “ “
TAIWAN “ “
October 15, 1997 79

3) All Production HKG CICS uses different SNT. The SNT are compiled using
Changeman packages. The package ids are as follows:
CICS Package Id Source

VISA HP11 PHKVISNT
BANK HP10 PHKBKSNT
DINERS HP10 PHKDISNT
MACAU HP20 PHKMASNT
TAIWAN HP30 PTWSNT
NOTE : Currently, the production SNT for VISA, TAIWAN, need to be compiled using direct
update after the Changeman process. This is temporarily to ensure that the
XCOM of the production loads is stabilized.
To compile directly, follow the instructions below:
a) Apply direct access to update PNCSG.*.TABLIB.* using dual control I ids.

b) Select member to be updated in production PDS - TNKH.CICS.TABLES
c) PHKVISNT for PRODVISA
d) PTWSNT for PRODTAWN
e) Update the member base on the request in STHK.MDC.CICS.REQUEST.
f) Assemble the SNT using the JCL in TNKH.JCL.CICS in production system.
g) PHKVIASM for PRODVISA
h) PTWVIASM for PRODTAWN
i) Copy the load modules produced in (4) in PNCSG.*.TABLIB.ONLINE to PNCSG.*.TABLIB
j) Issue memo for CICS refresh.
k) Rename the change request member in STHK.MDC.CICS.REQUEST to SMR NO. and input
change date and effective date in the member. Move the member to
STHK.MDC.CICS.RESPONSE.
October 15, 1997 80

6.10.23.CICS Suffixes
6.10.23.1. TEST for Version 2.1.2 and Version 3.3.0
Loadlib : STDC.MCI.LOD
CICS330.SDFHAUTH
Used / Available Suffix :

A1 TNACICS
B1 TDCCICS
B5 TRCCICS
C1 TSGCICA
DA
D1
D5
E1
F1 TICCICE
F5
G1 TPHCICT
H1 TTUCICI
I1 TINCIC1
I5 TINCIC2
J1
K1 TMLCICA
L1 TDCCICT
M1 TSBCICS
N1 TSGCICN
O1
P1
Q1
R1
S1 TSNCICS
T1 TSGCICT
U1 TGMCICT
V1 TGMCICI
W1
X1
X5
Y1
Z1
01
11
20
2T
21
22
31
51
61 TMLCIC1
71
80
81
82
October 15, 1997 81

6.10.23.2.TEST for Version 4.1.0
Loadlib : STDC.MCI.LOD.V410
SASY.MCM.LOD.R410.BASE0
Used / Available Suffix Used / Available Suffix Used / Avail Suffix

(1 and 3) : (6 and 8) : (4 and 5) :
A1 A6 TAECICR A4 TJPCICA
B1 TRCCICS B6 TAECICI B4 TJPCICI
C1 TTWCICR C6 TGBCICI C4 TJPCICN
D1 TTWCIC1 D6 TRBCIMD D4 DMBCICT
E1 THKCIC1 E6 TOZCICA E4 DMBCICI
F1 THKCIC2 F6 TRBCISI F4 DMBCIC2
G1 THKCICE G6 SRBCISI G4
H1 THKCICS H6 TRBCRSI H4
I1 TINCICI I6 SPLCICR I4
J1 TJPCIC1 J6 SRBCRSI J4
K1 TTHCIC1 K6 KRCICS K4
L1 TTHCIC2 L6 TNZCICI L4
M1 TPHCIC2 M6 TNZCICR M4
N1 TPHCIC1 N6 SAECICR N4
O1 TPHCICR O6 SAECICI O4
P1 TICCICE P6 SPKCICI P4
Q1 TPHCICI Q6 SPKCICR Q4
R1 TTWCICI R6 TRBCISF R4
S1 TINCICR S6 SINCICR S4
T1 SPHCICR T6 STHCICI T4
U1 SPHCICI U6 SINCICI T4
V1 TTHCICI V6 TTHCICR V4
W1 TOZCICR W6 STHCICR W4
X1 TOZCICI X6 STWCICR X4
Y1 TPKCICS Y6 STWCICI Y4
Z1 TAECICS Z6 SPLCICI Z4
01 06 TRBCRUW 04
10 TTUCICS 16 TTUCICT 14
20 TDCCICE 26 TRBCIY2 24
31 TGBCIC1 36 TRBCRY2 34
41 TTWCICS 46 44
51 TDCCICR 56 54
61 TPLCICR 65 TPLCICS 64
71 TPLCICI 76 SNZCICR 74
81 TPKCICR 86 SNZCICI 84
91 TPKCICI 96 THKCICI 94
October 15, 1997 82

6.10.23.3.UAT for Version 1,2,3 and 4

SADC.MCM.LOD.ACIC.BASE0 (all macros)
SADC.MCM.LOD.UCIC.BASE0 (V3 SIT)
SADC.MCM.LOD.A410.BASE0 (V4 SIT)
Used /Available Suffix (1 and 3 ) : Used /Available Suffix (6 and 8 ) :

A1 ATHCIC1 A6 AAECICI
B1 B6 AAECICR
C1 APHCIC1 C6 ATWCICI
D1 ASGCICI D6 ATHCICI
E1 ATUCICN E6 ATWCICR
F1 ATUCICS F6 ATHCICR
G1 ADCCICT G6 APKCICI
H1 ASNCICS H6 APKCICR
I1 AHKCICS I5 AINCIC1
J1 AJPCICS J6 APLCICR
K1 AHKCIC1 K6 APLCICI
L1 ATWCIC1 L6 ANZCICI
M1 ASBCICS M6 ANZCICR
N1 ATWCICS N6 AOZCICR
O1 ASGCICN O6 AOZCICI
P1 P6 AJPCICI
Q1 APHCICI Q6 AJPCICA
R1 ADCCICR R6 AJPCICN
S1 ARACICS S6
T1 APHCICR T6
U1 AJPCIC1 U6
V1 ASGCICA V6
W1 AAECICS W6
X1 APKCICS X6
Y1 AINCICR Y6
Z1 AINCICI Z6
01 ATUCICI 06
11 AGMCICI 16
20 AGBCICI 26
2T ASICICT 36
21 ASICIC1 46
22 ASICIC2 56
31 APLCICS 66
41 AKRCICS 76
51 UMBCICT 86
61 UMBCIC1 96
71 UMBCIC2
October 15, 1997 83

6.10.23.4.PRODUCTION for Version 1,2,3, and 4

Loadlib : SPSY.MCI.LOD.V170 ( all macros )
CICS330.SDFHAUTH ( V3 SIT )
SPSY.MCI.LOD.SITV410 ( V4 SIT)
Used / Available Suffix (1 and 3) : Used/Available Suffix (6 and 8) :
A1 PJPCICN A6
B1 B6
C1 PSNCICS C6
CP PSNCICP ( RRDF testing )
CX PSNCICX ( RRDF testing )
D1 PDCCICT D6
E1 PSGCICI E6
F1 PSGCICK F6
G1 G6
H1 PSBCICS H6
I1 PHKCICS I5 PHKCIC1
J1 PJPCICS J6
K1 PRACICS K6
L1 PINCICS L6
M1 PTUCICI M6
N1 PTUCICK N6
O1 O6
P1 P6
Q1 PPHCICS Q6
R1 PTWCIC1 R6
S1 PTUCICS S6
T1 PTHCICS T6
U1 PGMCICI U6
V1 PTUCICR V6
W1 PWACICS W6
X1 PPHCICR X6
Y1 PPHCICI Y6
Z1 PPLCICS Z6
01 PKRCICS 06
10 PSICICT 16
11 PSICIC1
12 PSICIC2
21 PJPCIC1 26
31 PJPCIC2 36
41 PTWCICS 46
51 PAECICS 56
61 PPKCICS 66
71 ZMBCICT 76
81 ZMBCIC1
91 ZMBCIC2
October 15, 1997 84

6.11.DFHRPL Library Concatenation Standards

6.11.1.RND - DFHRPL Library Concatenation Standards
6.11.1.1.AOR Region
//DFHRPL DD DISP=SHR,DSN=STcc.MSI.LOD *RND
// DD DISP=SHR,DSN=STcc.MNS.LOD *RND
// DD DISP=SHR,DSN=SAcc.MSI.LOD.CMPRM *UAT
// DD DISP=SHR,DSN=SAcc.MNS.LOD.CMPRM *UAT
// DD DISP=SHR,DSN=SAcc.MCM.LOD.ccSI.BASE0 *SI BASE
// DD DISP=SHR,DSN=SAcc.MCM.LOD.ccNS.BASE0 *NS BASE
// DD DISP=SHR,DSN=SARB.MSI.LOD.CMPRM *CMN REL PRM
// DD DISP=SHR,DSN=SARB.MNS.LOD.CMPRM *CMN REL PRM
// DD DISP=SHR,DSN=SARB.MCM.LOD.RBSI.BASE0 *CMN REL
// DD DISP=SHR,DSN=SARB.MCM.LOD.RBNS.BASE0 *CMN REL
// DD DISP=SHR,DSN=SAIC.MSI.LOD.DBCS *VAN BASE
// DD DISP=SHR,DSN=STDC.MCI.LOD.V410 *CICS TABS
// DD DISP=SHR,DSN=STcc.MAD.NATV228.LOAD *CUST NAT
// DD DISP=SHR,DSN=STDC.MAD.NATV228.LOAD *VAN NAT
// DD DISP=SHR,DSN=STDC.MAD.NDBV228.LOAD *VAN NATDB2
// DD DISP=SHR,DSN=CICS410.SDFHLOAD *IBM DEFLT
// DD DISP=SHR,DSN=CEE.V1R3M0.SCEECICS *LE370
// DD DISP=SHR,DSN=CEE.V1R3M0.SCEERUN *LE370
// DD DISP=SHR,DSN=CANDLE.TLOADLIB *CANDLE
// DD DISP=SHR,DSN=CW.CSS.R600.LOAD *CW SHR SERV
// DD DISP=SHR,DSN=CW.XPEDITER.R660.LOD.CIC410 *XPED
// DD DISP=SHR,DSN=CW.CICSAAFX.R210.SKFXCLIB *ABENDAID
// DD DISP=SHR,DSN=CICSTMC.LOD *TIME MACHINE
Note: cc represents country code
e.g. SAIN.MSI.LOD.CMPRM (Indonesia Systematic UAT promotion library)
DB2 subsystem used is D41T

Natural environment used is RND
6.11.1.2.TOR Region
// DD DISP=SHR,DSN=CICSTMC.LOD *TIME MACHINE
October 15, 1997 85

6.11.2.Pre-UAT and UAT- DFHRPL Library Concatenation Standards
6.11.2.1.AOR Region
//DFHRPL DD DISP=SHR,DSN=SScc.MCW.LOD *XPED
// DD DISP=SHR,DSN=SADC.MCM.LOD.AE41.BASE0 *APPL EXTS
// DD DISP=SHR,DSN=SADC.MCM.LOD.ACIC.BASE0 *CICS TABS
// DD DISP=SHR,DSN=SAcc.MAD.NATV228.LOAD *CUST NAT
// DD DISP=SHR,DSN=NATURAL.V228.NAT.LOAD *VAN NAT
// DD DISP=SHR,DSN=NATURAL.V228.NDB.LOAD *VAN NATDB2
// DD DISP=SHR,DSN=CICSTMC.LOD *TIME MACHccE
eg. SAIN.MSI.LOD.CMPRM (Indonesia Systematic UAT promotion library)
DB2 subsystem used is D41A

Natural environment used is UAT
6.11.2.2.TOR Region
//DFHRPL DD DISP=SHR,DSN=SAcc.MSI.LOD.CMPRM *UAT
// DD DISP=SHR,DSN=SADC.MCM.LOD.ACIC.BASE0 *CICS TABS
October 15, 1997 86

6.11.3.Training - DFHRPL LIBRARY CONCATENATION Standards
6.11.3.1.AOR Region
//DFHRPL DD DISP=SHR,DSN=SScc.MCW.LOD *XPED
// DD DISP=SHR,DSN=SAcc.MAD.NATV228.LOAD *CUST NAT

Natural environment used is UAT
6.11.3.2.TOR Region
//DFHRPL DD DISP=SHR,DSN=SAcc.MSI.LOD.CMPRM *UAT
October 15, 1997 87

6.11.4.Conversion - DFHRPL Library Concatenation Standards
6.11.4.1.AOR Region
// DD DISP=SHR,DSN=STcc.MAD.NATV228.LOAD *CUST NAT
// DD DISP=SHR,DSN=STDC.MAD.NATV228.LOAD *VAN NAT
// DD DISP=SHR,DSN=STDC.MAD.NDBV228.LOAD *VAN NATDB2

Natural environment used is RND
Conversion CICS does not have a TOR
6.11.5. PROD - DFHRPL Library Concatenation Standards
6.11.5.1.AOR Region
//DFHRPL DD DISP=SHR,DSN=SPcc.MSI.LOD.CMPRM *PROD
// DD DISP=SHR,DSN=SPcc.MNS.LOD.CMPRM *PROD
// DD DISP=SHR,DSN=SARB.MSI.LOD.CMPRM *CMN REL
// DD DISP=SHR,DSN=SARB.MNS.LOD.CMPRM *CMN REL
// DD DISP=SHR,DSN=SPIC.MSI.LOD.DBCS *VAN BASE
// DD DISP=SHR,DSN=SPSY.MCI.LOD.PE41 *APPL EXTS
// DD DISP=SHR,DSN=SPSY.MCI.LOD.V170 *CICS TABS
// DD DISP=SHR,DSN=SPcc.MAD.NATV228.LOAD *CUST NAT
// DD DISP=SHR,DSN=BMC3270.V2520.LOAD *DATA PACKER
DB2 subsystem used is D41P

Natural environment used is PROD
October 15, 1997 88

6.11.5.2.TOR Region
//DFHRPL DD DISP=SHR,DSN=SPcc.MSI.LOD.CMPRM *PROD
// DD DISP=SHR,DSN=SPcc.MNS.LOD.CMPRM *PROD
// DD DISP=SHR,DSN=SARB.MSI.LOD.CMPRM *CMN REL
// DD DISP=SHR,DSN=SARB.MNS.LOD.CMPRM *CMN REL
// DD DISP=SHR,DSN=SPIC.MSI.LOD.DBCS *VAN BASE
// DD DISP=SHR,DSN=SPSY.MCI.LOD.PE41 *APPL EXTS
// DD DISP=SHR,DSN=SPSY.MCI.LOD.V170 *CICS TABS
// DD DISP=SHR,DSN=BMC3270.V2520.LOAD *DATA PACKER
October 15, 1997 89

7. PROGRAMMING LANGUAGE STANDARDS

7.1. COBOL
The IBM host provides VS/COBOL, COBOL II and COBOL/370. COBOL/370 should be used as a
standard.
7.2. ASSEMBLER
No new program(s) will be coded in the Assembler language except for special purpose(s) like utilities
development and must have the approval of the Application Director.
7.3. NATURAL
Natural language program needs Application Director’s approval.
7.4. UTILITIES LANGUAGE
Easytrieve from Computer Associate.
SQL language for DB2 from IBM.
October 15, 1997 90

8. GUIDELINES FOR CHANGEMAN SET-UP

8.1. Pre-Setup Meeting
- Complete Request Form
- Agree on for Application Project-id Name
- Naming Standard for Promotion and Baseline libraries.
- Libraries Concatenation for Compiling Procedures setup
- Target Production Load libraries Name
- Approval Parties
Unit to assign representatives to work with APCC on the following:-
- Check compiling procedures

- Check Libraries concatenation
- Test each and every compiling procedures defined in new Project-id
- RACF interface
- XCOM interface
Unit representative will brief all application programmers on compiling procedure matrix before opening it
up for mass compilation.
Post - Setup Changes
- Inform APCC through Fax or CITIMAIL and highlight changes

e.g. Name of Compiling Procedure
Provide Sysout listing
Additional library to be concatenated
Additional compiling or Link-edit Option to be added
Note : Request that requires RACF interface will take a longer time to setup.
8.2. Project Managers To Include CHANGEMAN Compilation Time In Project Planning.
8.3. Application Project-ID Standard

The Application Project-id is limited to 4 characters only. In APCC, the first 2 bytes is normally used to
represent the country code and the last 2 bytes is used for application code.
e.g. Phxx
- PH represents the country Philippines
where xx = SI for Systematic Application.

NS for Non Systematic Application. (CHANGEMAN Only)
8.4. SIT Promotion Libraries

There are two levels of Promotion involved for systematic Project.
The first promotion will copy the components (Copybooks and
Objects modules) from the staging libraries to the SIT libraries.
This function is normally given to the Project Manager.
SIT libraries are pre-defined in CHANGEMAN and the naming convention are
SSxx.Myy.CPY.CMPRM (SIT Copybook library)
SSxx.Myy.LOD.CMPRM (SIT Load library)
where xx denotes the Country code

and yy is the Application code as below
- SI for Systematic Application(s)

- NS for Non-Systematic Application(s) (CHANGEMAN only)
8.5. UAT Promotion Libraries
The second level of Promotion will move the components (Copybook and Object modules) from the SIT to
the UAT libraries. This involves the APCC librarian to perform this function. UAT libraries are also pre-
defined in CHANGEMAN during the initial setup of the Application Project-id. The naming convention of
these libraries are :-
SAxx.Myy.CPY.CMPRM (UAT Copybook library)
SAxx.Myy.LOD.CMPRM (UAT Load library)

and yy is the Application code as below
- SI for Systematic Application(s)

- NS for Non-Systematic Application(s) CHANGEMAN only)
8.6. Baseline Libraries
Baseline libraries are set of libraries which can be considered as the Production copy. They are pre-
defined during the initial setup of the Application Project-id. There are two version of baseline libraries
created for each library type. The most current copy of the component is stored in BASE0 and the
previous copy is kept in BASE1. Updates to these libraries is done solely by CHANGEMAN itself upon
approval by all parties concerned.
The name of these libraries are :-

SAxx.MCM.yyy.aaaa.BASE0/1
yyy denotes the library type
SRC - Source
CPY - Copybook
LST - Compile listing
LOD - Load module
SRB - Source batch
TRB - Total Relationship Banking
GRB - Global Relationship Banking
DDM - Data Definition Module
INS - Insurance
DBB - DB2 Bind Control
DBR - DB2 DBRM
LOB - Load batch
PRC - Procedure libraries
aaa denotes the Application Project-id
8.7. Approval of Packages

For most Application Project-id, there are between 5 to 6 levels of approval defined.
They are :-
1) Programmer
2) Programmer Peer reviewer
3) Country User
4) Production Controller
5) Data Center Manager
6) Librarian
Approval of packages should be done only after Users have successfully conducted the UAT testing and
are ready to move the component to Production.
Pre-cutover meeting should be held at least two weeks before the live date of each major project.
9. STORAGE MANAGEMENT GUIDELINES
9.1. Introduction
The Storage Management Subsystem (DFSMS/MVS) is fully activated in all the LPARs.
9.2. SMS Classes and Groups
Data Class: Data definition
Storage Class: Availability and accessibility requirements
Management Class: Data migration, backup and retention
Storage Group: List of candidate allocation volumes
The following data classes are available in both production and RND/UAT systems:
DC001: Allocation for sequential data sets < 1,000 records

DC01K: Allocation for sequential data sets < 1 million records
DC10K: Allocation for sequential data sets > 1 million records
DC001V: Allocation for VSAM data sets < 1,000 records
DC01KV: Allocation for VSAM data sets < 1 million records
DC10KV: Allocation for VSAM data sets > 1 million records
Default for VSAM data sets is DCEXV. No default for non-VSAM data sets.
The maximum size for physical sequential file on a volume is 64,000 tracks. Please ensure that this limit
is not exceeded when using data class (in particular DC10K) for space allocation.
Data sets with suffix RRmmddRR are used for problem investigation and resolution, reorg etc. These data
sets will be migrated 3 days and expired 2 weeks after non-reference.
During rename of a data set, the management class will be updated. However, the data set is not moved,
ie it stays in the current volume.
9.3. House-Keeping Rules
Programmers are responsible to perform periodic house-keeping to

delete obsolete or redundant datasets.
Important Note:
Under SMS, dataset created with expiration date (i.e. EXPDT/RETPD or TO/FOR attributes) will be deleted
by DFHSM upon expiration of the dataset. Thus, we have nullified all expiration date and use SMS
management class to control the expiration of data sets.
Specify FREESPACE(0 0) to remove CI and CA free space during restore of production data to UAT. This
will reduce the disk space requirement
9.4. DFHSM Migration Policy
9.4.1. DFHSM MIGRATION POLICY FOR APCC PRODUCTION LPAR

DFHSM will perform daily housekeeping to migrate data sets that are not referred for a specified
period of time to either ML1 (on disk) or ML2 (on tape cartridge) volumes. Migration is based on
the last open date of the data set. The following table showed the data set retention period in
primary volume and ML1 volume:
Primary ML1 Data Set Expiration

Pool Volume Volume
System and software products No migration Nil Nil
Application data sets (exclude GDG) No migration Nil Nil
GDG (see note 2) 35 days 7 days Delete rolled-off (i.e. excess) GDG
Load libraries No migration Nil Nil
TSO data sets 7 days 7 days Nil
Backup data sets (see note 3) 4 days Nil Nil
DB2 system data sets No migration Nil Nil
Temporary ISPF log and listing data 3 days Nil Delete if not reference after 3 days
sets
Re-run data sets (with suffix 3 days Nil Delete if not reference after 14 days
RRxxxxRR)
Note :
1. All system volumes are backup on a weekly basic. Two generations are being kept.
2. The two most recent GDG will stay on primary volumes for 37. The older generations are
eligible for early migration if space is needed to meet the volume threshold during space
management process.
3. Data sets with the followings suffix are considered as backup data sets:
APR9*, AUG*, BACKUP*, BK, BKL*, BKP*, BU, BKUP*, BUP*, DEC9*, FEB9*, FIX, JAN9*,
JUL9*, JUN9*, MAR9*, MAY9*, NEW*, NOV9*, OCT9*, OLD*, ONETIME*, REORG, SEP9*,
TEMP*, TEST, TMP*.
The GDG for the followings suffix are considered as backup data set:
BU, BKP, BKUP.
9.4.2. DFHSM MIGRATION POLICY FOR APCC RND/UAT LPAR

DFHSM will perform daily housekeeping to migrate data sets that are not referred for a specified
period of time to either ML1 (on disk) or ML2 (on tape cartridge) volumes. Migration is based on
the last open date of the data set. The following table showed the data set retention period in
primary volume and ML1 volume:
# of
Primary ML1 Backup
Pool Volume Volume Versions Data Set Expiration

(note 1)
System and software products No migration Nil Nil Nil
RND Online application data sets 30 days 14 days 0 Delete if not reference after 7
(exclude GDG) months (see note 2)
RND Batch application data sets 14 days 14 days 0 Delete if not reference after 7
UAT/SIT Online application data 30 days 14 days 0 Delete if not reference after 13
sets (exclude GDG) months (see note 2)
UAT/SIT Batch application data sets 14 days 14 days 0 Delete if not reference after 13
Paraller RND/UAT data sets 30 days 7 days 0 Delete if not reference after 2
months (see note 3)
GDG (see note 4) 21 days 7 days Nil Delete rolled-off (i.e. excess) GDG
Load libraries 30 days 14 days 2 Nil
TSO data sets 30 days 7 days 1 Nil
Backup data sets (see note 5) 4 days Nil Nil Nil
DB2 system and Changeman No migration Nil Nil Nil
system data sets
Changeman baseline libraries No migration Nil 7 Nil
Changeman audit files 37 days Nil 2 Delete after 1 year (see note 3)
Changeman staging libraries 90 days 30 days 2 Delete after 2 years (see note 3)
Temporary ISPF log and listing data 3 days Nil Nil Delete if not reference after 3
sets days
Re-run data sets (with suffix 3 days Nil Nil Delete if not reference after 14
RRxxxxRR) days
Note :
1. Number of backup versions indicates the maximum number of backup versions that can be
kept for an existing data set. The data set will be backed up during DFHSM automatic
backup process if it has been changed. (DFHSM automatic backup runs everyday). All
volumes are backup on a weekly basic. Two generations are being kept.
2. The most recent backup copy (by user) will be kept for 90 days after the data set is deleted.
3. The most recent backup copy (by user) will be kept for 30 days after the data sets is deleted.
4. The two most recent GDG will stay on primary volume for 21 days. The older generations
are eligible for early migration if space is needed to meet the volume threshold during space
management process.
5. Data sets with the followings suffix are considered as backup data sets:
APR9*, AUG*, BACKUP*, BK, BKL*, BKP*, BU, BKUP*, BUP*, DEC9*, FEB9*, FIX, JAN9*,
JUL9*, JUN9*, MAR9*, MAY9*, NEW*, NOV9*, OCT9*, OLD*, ONETIME*, REORG, SEP9*,
TEMP*, TEST, TMP*.
9.5. SRS/ACC
SRS/ACC is used for disk space allocation failure. The following message will be issue by
SRS/ACC if insufficient disk space is available on a volume to support the allocation:
ACC28100-A PRIMARY SPACE REDUCED FROM xxx TO yyy CYL

or ACC24100-A SECONDARY SPACE REDUCED FROM xxx TO yyy CYL
When the data set reaches 16 extents or no space is available on the current volume,
SRS/ACC performs an ADDVOL dynamically and the following message will be issued:
ACC20600-A VOLUME * WAS ADDED TO DATA SET
Job will then continue to run. SRS/ACC can add up to 49 volumes.
Note: DFSORT (work files), SAS (work files), EZTRIEVE (temp files) programs do not
support dynamic ADDVOL. The job will abend with Sx37 with the following message when the
data set reaches 16 extents on a volume or no space is available on the current volume:
ACC20625-E DCB IS USING EXCP

or ACC20626-E DCB IS USING NOTE/POINT
If you are using these programs with large file, the recommendation is to specify
UNIT=(SYSDA,5) in the JCL to pre-allocate the data set and allow the data set to expand into 5
volumes, if necessary.
For SORTWK, it is recommended to use dynamic sort work and specify the number of files
required (default is 16).
SORTWK file limitations and recommendations

DFSORT bases the amount of work space it dynamically allocates on the number of bytes to be
sorted, which is the input file size. For variable length records, DFSORT uses one-half of the
maximum record length to determine the input file size (unless AVGRLEN option is specified in
the JCL). If the actual average record length is significantly different from one-half of the
maximum record length, specifying AVGRLEN=n can prevent DFSORT from over or under
allocating dynamic sort work space.
In general, DFSORT can automatically make an accurate determination of the file size by
determining the number of input records. However, there are several cases that DFSORT cannot
determine the accurate input file size (eg input data sets are on tape, input data sets are members
of partitioned data sets, a spool DD input data set is present). DFSORT may dynamically over-
allocate or under-allocate the work space, leading to wasted space or an out-of-space abend,
respectively. If such cases, you should specify either the exact number of records to be sorted or
an estimate of the number of records to be sorted. There are several ways to specify the number
of records to be sorted at run-time. We recommend that we use SIZE=En or FILSZ=En where n =
number of records in the input file. FILSZ works the same way as SIZE except that the record
count you specify should take into account not only the number of records in the input data sets,
but also, if significant, the number of records of inserted or deleted before sorting. If FILSZ/SIZE
is specified, DFSORT always uses it.
10. APPENDICES
10.1. Appendix A - Country Codes

A two-byte code identifying the country or installation specifics:
Bank Control
Code Records No. Country
AE 78 United Arab Emirates (Gulf)

AD Adabas
BN 73 Brunei
BR Sabre Teller
80 Bahrain
CZ 48 Czechoslovakia
DC Data Centre
GB Global Cardpac Base
HB Hong Kong Banking
HK 88 Hong Kong
HU 60 Hungary
GM 11 Guam
IC Integrated Computer Banking System
(ICBS)
ID 21 India
IN 33 Indonesia
JP 28 Japan
KR 77 Korea
MA Macau
MB Multi-Branch PBG Group (Zurich)
ML 38 Malaysia
NA New Applications
NZ 31 New Zealand
OZ (AU) 24 Australia
79 Oman
PH 07 Philippines
PK 92 Pakistan
PL 70 Poland
RA Auditor
RB N/A Global Relationship Banking
RC Regional Citiplus
SB 96 Samba (Saudi Arabia)
SI Singapore PBG
SG Global Banking (Singapore)
SN 18 Singapore
SY Systems / DPC Related
TH 09 Thailand
TU 05 Turkey
TW 86 Taiwan
WA West Asia
NB : Country codes in parenthesis are for old systems.

10.2. Appendix B - Application Codes

A two-byte code identifying a particular application or system as follows:
Code Application System
AA CICS Abend-Aid
AD ADABAS
AF Asia Frequent Flyer (AFF)
AM Advanced Loans System
AO AF/Operator
AP Accounts Payable
AT ATM or CAT System
AX Australia Tax
BB Basic Banking System
BC Business Cards
BD BDMS (Billing Dispute Management System)
BF BAFES Interface - Batch
BH Behaviour Score
BI BAFES Interface - Online
BL Business Liabilities
BP Balance of Payments
BN HongKong Banking Application
BR SABRE
BT BTAM
C1 Tape Management System (CA/1)
C2 CORE 2
CA Computer Assisted Collection System (CACS)
CD CICS Debug-Aid
CE Emergency Fix (Library)
CG Catalog Solution
CH Cheque Disbursement System
CI CICS System Dataset
CL Consumer Loans System (CLS)
CM Changeman
CN CANDLE Products
CO PBG Cosmos
CP CARDPAC
CQ CitiQuest
CR Citi-Remitter
CS Combined Statements
CT CitiPlus
DA Direct Access (INFOBOT)
DB Database (DB2)
DC Electronic Data Exchange (EDC)
DD Diner EDC
DE Data Entry
DF Data Facility (DF) group of product(s)
DH Diners Franchise
DN Diners System
DO Diner OLA (Online Authorization)
DR RRDF for Diners OLA
DS Deposits System
DT Document Tracking System
DW Data Warehouse
EC Executive Computing Products
ED Edit Package
EF IEF
EM PBG EMS
ES Citicard System
EZ Easytrieve Plus
FA File-Aid
FC Foreign Currency Statistical Codes
FM Financial Management System
FR CICS/VSAM Forward
FS IBM 4700 Financial Communication System Host Support
FT Funds Transfer
FX Foreign Exchange
GA General Applications (For Turkey & Guam Systematics)
GB Card Global Application
GC GCB (COSMOS Related Systems)
GL GL/MIS
GN Architecture System(s)
GO GO System for Hong Kong
GR GIRO / Standing Instruction
GT GTA Software
HR Human Resources Payroll System
HS HSC (SILO Software)
IA Investigation Automated System
IF Customer Information File

II Insurance Information System
IM IMPACS
IN ITS (Interchange Tracking System)
IO IOA (Integrated Operations Architecture)
IR Item Reconciliation
IS Systematic Information Management System
IT Intersystem Transfer
IV Check Inventory
KO Online Collections
LG Logout
LN Consumer Loans System
MA MIS
MD Multi-currency Deposit
MF Mutual Funds
MG PBG Margin System
MH MHPF (Member Host Preparation Facility)
MI Monetary Interface Allen
MM Money Market
MS Citibank SMS
MT MTS (Memo Tracking System)
NA NAS (New Account System)
NC NCP
ND NDM
NO Automated Network Operations (ANO)
NV NetView
NX Exchange Rate System
OA Online Authorization System (OLA)
OC Automated Operations Control (AOC)
OD Control-D
OF Orbit Funds Host Interface
OL Merge Old Phase (Library)
OM Omegamon
OP OP/ESA
OW Origination and Warehouse
PA Panvalet
PB CICS Playback
PM Problem Management (during MVS Conversion)
PR Backup
RB GRB (Global Relationship Banking)

RC RACF
RE Real Estate
RF Card Reference
RI Ready Credit Interface
RM Customer Information System
RP Relationship Pricing
RR RRDF for OLA
RS RMS (Recovery Management System)
RW Reward
S2 Screen Definition Facility (SDF2)
SA SRS/ACC
SC Customer Statement
SD Safe Deposit Box
SE Sabre Platform
SF Share Finance
SG SG-Control
SI Systematics
SL Security Loans
SM Customer Service Management
SP SABRE Platform Interface

SR Service Level Reporter (SLR)
SS Security Subsystem
ST Savings / Time System
SY System
SU CitiPlus Support Unit Application
SV Signature Verification
TD TSO Debug-Aid
TI Turkey Invoice Application
TL Transaction System Teller
TP TPIN Subsystem
TR Tax Reporting System (ICBS Development)

TS/GN Transaction System Delivery / GN
TX Tax Reporting System (Systematics)
UR URMN
VP VTAMPRINT
VS VSAM
VT VTAM
WC World Cash Card
XB Card X-Border Processing
XC XCOM
XI Forms Printing
ZE Zeus Application
ZZ PBG SPITAB
10.3. Appendix C - Standard Report Format -- Non-Systematics
Standard Report Format - Non-Systematics
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
1 2 3 4 5 6 7 8 9 10 11 12 13
PROCESSING PROGRAM ID
|
V
XXXXXXXX CITIBANK NA, SINGAPORE PAGE NO ZZZ9

XXXXXXXXXXXXXXXXXXXXXXX PROCESSDATE DD/MM/YY
XXXXXXXXXXXXXXXXXXXXXXX
|
V
--------------------- END OF REPORT ---------------------

10.4. Appendix D - Standard Report Format - Systematics
Standard Report Format - Systematics
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
1 2 3 4 5 6 7 8 9 10 11 12 13
CONTROL 1 REPORT TITLE PROCESSING PROGRAM ID

l l l
V V V
BANK 999 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX *XXXXXXX* PAGE NO ZZZ9

XXX 999 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX PROCESS DATE DD/MM/YY
l XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX PROCESS THRU DD/MM/YY
V
CONTROL 2
10.5. Appendix E - Sample Layout Of Header and Trailer Records In Interface Files
LEVEL NO. DESCRIPTION SIZE COMMENTS

01 Header Record
05 Header Record Type X(03) ‘HDR’
05 Header Processing date 9(08) Format CCYYMMDD.
Checking against business date is mandatory to
ensure that right file is being processed.
05 Filler X(190) Length of filler can vary depending on the input file
01 Trailer Record
05 Trailer Record Type X(03) ‘TRL’
05 File Name X(08) Optional. Should be unique for each input file.
05 File Creation Date 9(08) Format CCYYMMDD
05 File Creation Time 9(06) HHMMSS
05 Hash Amount S9(13)v99 Hash algorithm can vary but must match with the
receiving program logic. Checking on hash
amount is mandatory for files with financial
information.
05 Record Count 9(09 Inclusive of header and trailer records. Checking of
record count is mandatory.
05 Account Hash 9(09) Optional. Additional check to ensure data integrity.
05 Filler X(137) Length of filler can vary depending on the input file.
10.6. Appendix F - Data Center Operation Job Documentation
JOB NAME ==> ISSUE DATE ==>
JOB FUNCTION = = >
CRITICAL TO ONLINE ENVIRONMENT? (Y/N) = = >
FREQUENCY (DAILY/WEEKLY/MONTHLY/YEARLY/REQUEST) = = >
DAY OF WEEK (SUN/MON/TUE/WED/THU/FRI/SAT) = = >
DAY OF MONTH/YEAR = = >
PREDECESSOR(S) = = > _________ _________ _________ __________

_________ _________ _________ __________
_________ _________ _________ __________
SUCCESSOR(S) = = > _________ _________ _________ __________

_________ _________ _________ __________
_________ _________ _________ __________
SPECIAL INSTRUCTIONS = = >
Data Retention Scheduling
FILE(S) TO BACKUP :
______________________ _____________________ ___________________
_______________________ _____________________ ___________________
_______________________ _____________________ ___________________
_______________________ _____________________ ___________________
BACKUP RETENTION ==>
GDG LIMIT ==>
Job Steps Description
PROC NAME STEP NAME PROGRAM EXP MAX RECOVERY PROCEDURE

CC CC
10.7. Appendix G - Report Distribution
JOBNAME STEP SYSOUT REPORT NAME FORM RECIPIENT START Line,

No. TYPE Col
10.8. Appendix H - Production Job Modification Request Form
CITIBANK N.A. - ASIA PACIFIC COMPUTER CENTER

PRODUCTION JOB MODIFICATION REQUEST
TO: COUNTRY: DATE:
FROM: TEL: APPL:
PGMER APPROVED BY OPCA CHANGES:

INITIAL: CTY RM / SM: YES / NO
JCL CHANGES: YES / NO SAMPLE JCL ATTACHED NUMBER OF
PERM / TEMP YES / NO COPY FAXED
REASON RECOVERY PROCEDURE ATTACH:
YES / NO
JOB DESCRIPTION:
OPCA DEPENDENCY CHANGES/ADD: OPCA VERIFICATION BY RM/PM

CHECKED BY:
RM/PM INIT :
DATE/TIME :
REMARKS :
FOR PRODUCTION CONTROLLER USE JCL REMARKS.

PC CHANGEMAN
INIT PACKAGE NO:
G:\COMMON\PRODCTRL\PCFORMZ.DOC
Back Page of Production Job Modification Request
PROCEDURE
1. THIS FORM IS FOR THE FOLLOWING PRODUCTION REQUEST

- RUNNING ADHOC JOBS
- RUNNING NEW JOBS
- JCL CHANGES
- OPCA DEPENDENCY CHANGES
- NEW OPCA REQUIREMENTS
2. INDICATE THE PC’S NAME AT THE ‘TO’ COLUMN
3. WRITE YOUR NAME & COUNTRY SUPPORT CLEARLY AND SIGN
4. OBTAIN RM/SM SIGNATURE
5. STATE THE APPLICATION TYPE

- CP/OLA/NAS/CACS/RMS/MIS/SYSTEMATIC/SBOS
6. STATE THE TOTAL NUMBER OF COPIES FAXED
7. STRIKE OFF YES OR NO FOR:

- OPCA DEPENDENCY CHANGES
- JCL CHANGES
- SAMPLE ATTACHED (JCL)
8. CANCEL PERM OR TEMP FOR JCL CHANGES TO BE MADE
9. PROVIDE REASONS FOR CHANGES
10. STATE CLEARLY ALL CHANGES IN THE JOB DESCRIPTION COLUMN
11. RM/SM TO REVIEW OPC CHANGES AT 5PM & SIGN AT THE OPCA
VERIFICATION COLUMN
12. FAX BACK TO APCC IF THERE IS OPCA CHANGES/VERIFICATIONS.

10.9. Appendix I - RACF Profile Application
RACF PROFILE REQUEST FORM

REQUESTOR SECTION
DEPARTMENT COUNTRY SUPERVISOR ‘s NAME/ EDP QA
NAME
_____________________________________
REVOKE DATE TELEPHONE NUMBER SUPERVISOR’S SIGNATURE

USERID
___________________________________
(leave blank for new ID)
( ) PERMANENT STAFF ( ) CONTRACT STAFF
SIGN
___________________________________ SIN APCP SIN OLA PROD SIN SDCT rnd/uat SIN APCT rnd/uat
 HKG PROD  HKG QA / UAT  HKG RND
 AUST PROD - TSOP  AUST RND / UAT - TSOD

**note: for new programmer ID , pls attach ‘application access section’ form
REASON FOR REQUEST:
DATE
____________________________________
GROUP PROFILE USER PROFILE DATASET/GEN. RESOURCE
( ) ADD NEW GROUP ( ) ADD NEW PROFILE ( ) ADD NEW RESOURCE

( ) RESET /CHANGE PASSWORD
( ) DELETE GROUP ( ) RESUME /ENABLE PROFILE ( ) PE EXISTING RESOURCE
( ) REVOKE PROFILE
( ) DELETE PROFILE ** PLEASE COMPLETE
( ) CHANGE GROUP ( ) CHANGE PROFILE DETAILS
( ) TSO ( ) XCOM BELOW
DATASET / RESOURCE REQUEST

GENERAL RESOURCE DATASET
CLASS RESOURCE NAME REA/UPD/ALT DATASET NAME REA/UPD/ALT APF LLA
ADMINISTRATOR SECTION
AU RND/UAT / PROD
OTHERS __________________________________________________________________ SIN RND/UAT CINTECH / SDC / PROD

__________________________________________________________________ HK RND / UAT / PROD
__________________________________________________________________ GRPID CREATED ________________________
__________________________________________________________________ DATE __________________________________
__________________________________________________________________ SIGN ___________________ _______________
APCC SECURITY ADMIN DEPT. FAX 65- 770- 3597 TEL.ALI KALENI 65-770-3443 ( TAN GEOK KEE / JOANNA NG / ANGELA LIM ) 65-770-3533
winword 25/feb 96/racform.doc/ updated Jan 1997 by AL

RACF PROFILE APPLICATION PROCEDURE
1. Obtain a blank Racf profile request form from APCC Security Administration Unit. Please refer to Racf Profile
Request Form.
2. Complete the REQUESTOR SECTION.

a) NAME - requestor’s name.
b) USER ID - requestor’s User ID ( to leave blank if new ID).
c) SIGN - requestor sign here.
d) DATE - date of application.
e) DEPARTMENT - requestor’s department
f) COUNTRY - country of requestor.
g) SUPERVISOR’S NAME - requestor’s supervisor
h) REVOKE DATE - when to remove requested access
i) TELEPHONE - requestor contact number.
j) SUPERVISOR’s SIGNATURE- requestor’s supervisor sign here.
k) SYSTEM - write down system where User-id/Access is to be given; not allowed to tick or circle
l) PURPOSE - purpose or reason or functions for the User-ID (Must be indicated)
3. Complete the GROUP, USER, DATASET/GENERAL RESOURCE section

a) GROUP PROFILE - add - new group
- delete - obsolete group
- change - group data
b) USER PROFILE - add - new user profile

- reset password - password forgotten
- resume profile - id revoked
- revoke profile - not required
- delete profile - obsolete profile
- change profile - user profile info
- tso - need TSO segment
- xcom - need XCOM
c) DATASET/GENERAL RESOURCE
- add - new dataset or general resource
- access requirement- Read / Update / Alter (select one only)
1) General Resource Profile

Racf definition - name of program, terminal, transaction, command
2) Dataset Profile
Racf definition - name of dataset / file you need to access.
4. For Application Programmers, please complete APPLICATION ACCESS SECTION
5. Leave “ADMINISTRATOR SECTION” blank.
6. After completing Steps 1, 2, & 3, please send the form to APCC SECURITY ADMINISTRATOR.
Application Programmers to complete step 4.
7. APCC Security Administrator will inform requestor once it is done.
Note: Access Levels

Read - Can only read datasets
Update - Can read and update datasets
Alter - Can delete and define datasets
obsolete - APPLICATION ACCESS SECTION

APPLN PGMR GROUP = PGMRAPPL SYSTEM :( ) sin apct ( ) sin sdct
( ) hkgt ( ) aust tsod
APPLN PGMR NAME/USER-ID __________________________ MAIN COUNTRY SUPPORTING ............................................................
PGMR-TEAM ( ) / MGMT-TEAM ( )
NOTE : PGMR-TEAM (only UPDATE access to program library datasets eg. STxx.Myy.* )
MGMT-TEAM (ALTER access to program library datasets - can delete / define program libraries)
xx - cty code
yy - appln code
** Please tick ( ) against countries and applications supporting
## DB2 - submit to DB2 admr.
CITY/APPL CPAC OLA NAS CACS SAS RMS ADABAS SMTICS DB2 CHGMAN
xxMGMT ## APPRVL
xxPGMR PGMR? PEER?
1. SPORE
2. GCB
3. BKK
4. JKT
5. PHIL
6. JAPAN
7. SAMBA
WA
8. UAE WA
9. PAK WA
10. GUAM
11. HK
12. AUST WA
13. PBG SIN
14. PBG HK
15. MALAYSIA
16. PGMRTCS
17. KOREA
WINWORD/racform
OTHER INFORMATION - (REQUIRED ONLY FOR NEW PROJECTS) * TO BE COMPLETED BY PROJECT MANAGER
1. CICS-STARTUP NAME .................

2. CITIBK-SMS ( ) / RACF EXTERNAL SECURITY ( )
3. CICS-VERSION
4. DATASET/LIBRARY NAMING CONVENTION .................
APPLICATION ACCESS SECTION
APPLN PGMR NAME ______________________

I. Business Support GROUP (UNDER PGMRAPPL)
NO BUSINESS/DEV PRE-DEFINED TICK NO BUSINESS/DEV PRE-DEFINED TICK
TEAM GROUPNAME SELECT TEAM GROUPNAME SELECT
1 VISA CARDS PGMRCARD 6 TATA / TCS PGMRTCS
2 GCB BANKING PGMRBANK 7 ATO PGMRATO
3 ICBS BANKING PGMRICBS 8 MALAYSIA PGMRMSIA
4 PBG SIN PGMRSBOS 9 Cards (composer) PGMRIEF
5 PBG HKG PGMRSBOH 10 Mutual Funds PGMRMF
CICS
II. COUNTRY SUPPORT GROUP please select (tick) ## DB2 - submit to DB2 admr. APPLICATION
N0 COUNTRY CTRY CHGMAN ADA-BAS DB2 USR DB2 Sxx CIC n
CODE GROUP pgmr gt_____u Admr S=T(TEST)
PGMR MGMT PGMR PEER (+ntcm) gt_____a S=A(UAT)
see note$$ xx = CTY
n = SUFFIX
(optional)
1. SIN CARD SN
2. SIN BANK SG
3. SHARE FINANCE SF
4. REG CITIPLUS RC
5. PBG HKG MBHK
6. PBG SIN MB
7. BKK CARD TH
8. JKT CARD IN
9. PHIL CARD PH
10. JAPN CARD JP
11. JAPN BANK GC
12. SAMBA WA SB
13. UAE WA AE
14. PAK WA PK
15. GUAM GM
16. HKG BANK (GO) HK
17. HKG CARD HK
18. TWN OLA TW
19. TWN ECS TW
20. AUST WA AU
21. KOREA KR
22. MUTUAL FUNDS MF
NOTE : PGMR-TEAM (only UPDATE access to program library datasets eg. STxx.Myy.* ) ?? STDC.MIC.*.
(ALLOCATE)
$$ MGMT-TEAM (ALTER/DEFINE access to program library datasets - can delete / define program libraries)
III. GRB PROGRAMMER GROUP - GTxxGRBA / GSxxGRBA in G system

NO AE GM IN OZ PK PL TH TW
(UAE) (Guam) (Indonesia) (Australia) (Pakistan) (Poland) (Thailand) (Taiwan)
1.
IV. GLOBAL APPLICATION GROUP (VISA CARDS ONLY)

NO APPLICATION APP PRE-DEFINED GROUP (GLOBAL) IF NOT GLOBAL ONLY
CODE PGMR MGMT COUNTRY SPECIFIC APPL
1 SAS/MIS SAS
2 RCVRY MGMT RMS
3 COLLECTION CACS
4 OLA OLA
5 GLOBAL GB
OTHER INFORMATION - (REQUIRED ONLY FOR NEW PROJECTS) * TO BE COMPLETED BY PROJECT MANAGER
1. CICS-STARTUP NAME .................
2. CITIBK-SMS ( ) / RACF EXTERNAL SECURITY ( )
3. CICS-VERSION .................
4. DATASET/LIBRARY NAMING CONVENTION .................
WINWORD\racform.doc updated Nov 1996 by AL

10.10. Appendix J - APCC SLA Development Work
APPC TASK SETUP MODIFICATION RESPONSIBILITY

LEAD TIME WORKING DAYS WORKING DAYS
RND SIT UAT PRD RND SIT UAT

CHANGEMAN 20 4 4
GRB APPC
SETUP APPLICATION ID APPC
RACF APPC
MINOR CHANGES APPC
USER SIGN OFF 10 2 2 DEVELOPMENT TEAM
VTAM/NCP 14 14 14 14* 10 10 10
XCOM APPC
SABRE APPC
3270 APPC
EMBOSSER APPC
CICS PRINTER APPC
AVR APPC
X25 BAFES, NEW LINE* APPC
SDLC LINK / NCP GEN * APPC
USER SIGN OFF 7 7 7 7* 7 7 7 DEVELOPMENT TEAM
CICS 17 17 19 19 11 11 11
MRO APPC
APPC LU6.2 APPC
RACF APPC
NATURAL DASD APPC
SOFTWARE TOOLS APPC
DB2 SYSTEM APPC
GRB DB2 APPC
USER SIGN OFF 7 7 7 7 7 7 7 DEVELOPMENT TEAM
STORAGE 4 4 4 4 2 2 2 APPC
ADMINISTRATION
USER SIGN OFF 2 2 2 2 2hr 2hr 2hr DEVELOPMENT TEAM
STRATUS 11 11 11 14 4 4 4 APPC
USER SIGN OFF 7 7 7 10 DEVELOPMENT TEAM
SCHEDULER 14 9 10 5 5
DEFINITION OF JCL LIBS APPC
TO OPCA
SCHEDULE DEFINITION APPC
FLOWCHART APPC
USER SIGN OFF 4 4 5 2hr 2hr DEVELOPMENT TEAM
BATCH 10
DOCUMENTATION DEVELOPMENT TEAM
JCL CHANGES DEVELOPMENT TEAM
UAT CYCLE BATCH 14 APPC

Hrs
* PLUS TIME FOR NCP LOAD REFRESH, EVERY SECOND SUNDAY OF THE MONTH
10.11.Appendix K - Format for Interface File Header and Trailer

Records
Header Record Layout:
LEVEL NO. DESCRIPTION PICTURE REMARKS

01 Header Record
05 Header Record Type X(01) ‘HDR’
05 File Name X(08) Unique for each input file
05 Header Processing Date 9(08) YYYYMMDD
Checking against business date is
mandatory to ensure that right file is
being processed.
05 File Creation Date 9(08) YYYYMMDD
05 Filler XX Length of filler can vary
depending on input file.
Trailer Record Layout:
LEVEL NO. DESCRIPTION PICTURE REMARKS
01 Trailer Record
05 Trailer Record Type X(03) ‘TRL’
05 File Name X(08) Unique for each input file
05 Trailer Processing Date 9(08) Same as header processing date.
05 File Creation Date 9(08) YYYYMMDD
05 Record Count 9(09) Inclusive of header and trailer
records. Checking of record count is
mandatory.
05 Hash Amount 9(13)V99 Hash algorithm can vary but
must match with receiving
program logic. Checking of hash
amount is mandatory for files with
financial data.
05 Account Hash 9(09) Optional. Additional check
for data integrity in file.
05 Filler XX Length of filler can vary
depending on input file.

Dev Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dev Guide

Uploaded by

Copyright:

Available Formats

ASIA PACIFIC PROCESSING CENTER

GCB DEVELOPERS’ GUIDE

GLOBAL CONSUMER BANKING

Copyright  (1996) by Citibank N.A.

Change Control Date Section Change Description

April 16, 1997 2

3. DATASET NAMING STANDARDS..................................................................................................... 13

October 15, 1997 3

October 15, 1997 4

6.2.7. Emergency Update Procedure............................................................................................... 58

October 15, 1997 5

October 15, 1997 6

October 15, 1997 7

3. DATASET NAMING STANDARDS.........................................................................................................

October 15, 1997 8

5.5. BATCH......................................................................................................................... MUSTAFA SIDEK

October 15, 1997 9

5.15.2.System/Application Flow Chart................................................................................ JEFFREY GOH

October 15, 1997 10

6.10.12.1. ICBS Group............................................................................................................................. IAN LE

October 15, 1997 11

10.1. APPENDIX A - COUNTRY CODES.................................................................................. JEFFREY GOH

October 15, 1997 12

October 15, 1997 13

3. DATASET NAMING STANDARDS

3.1. TSO Datasets

3.2. Card / Non Systematics Systems Application Datasets

B The nature of the dataset as follows:

CC Identifies the country code.

N The type of dataset and can be either of the following:

TT The type of application.

xxxxxxxx 1 to 8 characters unique qualifier.

October 15, 1997 14

3.3. Banking Systems (Systematics) Application Datasets

B The nature of the data set as follows:

CC Identifies the country code.

MID is 5 characters in length

The 3rd character is a ‘.’

4th and 5th characters represent the receiving application.

GRP is 3 characters in length

Standards: V* = VSAM file

October 15, 1997 15

3.4. Application Libraries

Libraries must have the following naming conventions:

B The nature of the dataset:

CC Identifies the country code.

M A constant indicating that the dataset is a library.

TT Identify the type of application.

PRM System or Parameter library

October 15, 1997 16

- Two level of approval (PC and APPLN)

- UAT JCL/PROCS/PARMlib/User PARMlib will be copied directly from RND to UAT. No

- JCL/PROCS/PARMlib/User PARMlib will be staged in Changeman baseline library for

SP will advise on the impacts to this library name changes related to

ENV JCL PROCS PARMlib User PARMlib

- Separate application library will be used in RND (by application)

ENV JCL PROCS PARMlib User PARMlib

October 15, 1997 17

4. JOB RELATED STANDARDS

4.2. Job Initiator Standards

4.3. Job Names

An eight-byte name which identifies the job name:

October 15, 1997 18