IMS Tower

Procedure’s & Guidelines

PITNEY BOWES

Prepared By
Wipro Technologies

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 1 of 46

 Procedure’s & Guidelines

Confidentiality

This document is being submitted to Pitney Bowes by Technologies, with the explicit
understanding that the contents would not be divulged to any third party without prior written
consent from Technologies

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 2 of 46

 Procedure’s & Guidelines

APPROVAL SIGN-OFF

The above referenced deliverable has been reviewed and accepted by:

Name(s) Date

Technologies

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 3 of 46

 Document History

Version Date Author Comment Reviewed by

V1.0 May 31st 2007 Wipro Initial Draft Wipro
V1.1 Dec 1st 2009 Amitha Started using mymail.pb.com link for mail Chandra
communication and Lotus Notes was
stopped.
V1.2 Jan 1st 2012 Amitha New remedy tool created by Wipro will be Chandra
used in place of Old remedy tool.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 4 of 46

 Procedure’s & Guidelines

TABLE OF CONTENTS

Preface............................................................................................................................................................ 6
Chapter 1 - Introduction................................................................................................................................ 7
1.1 The Project............................................................................................................................................ 7
1.2 The Scope............................................................................................................................................. 7
Chapter 2 - Project Details........................................................................................................................... 8
2.1 Project Phases....................................................................................................................................... 8
2.2 Technical Environment................................................................................................................... 8
2.3 PB Development Environment........................................................................................................ 9
2.4 Application Summary.................................................................................................................... 24
Chapter 3 - Current Maintenance Process................................................................................................. 25
3.1 Change Request (CR)......................................................................................................................... 25
3.1.1 CR Impact & Estimation............................................................................................................... 25
3.1.2 CR Scheduling............................................................................................................................. 25
3.1.3 CR Implementation...................................................................................................................... 26
3.2 Ticket................................................................................................................................................... 26
3.3 Application coding................................................................................................................................ 26
3.4 Pitney Bowes IBM coding standards................................................................................................... 26
3.5 Testing................................................................................................................................................. 26
3.5.1 Application Testing...................................................................................................................... 26
3.5.2 Component Testing..................................................................................................................... 27
3.5.3 System Testing............................................................................................................................ 27
3.6 Tools............................................................................................................................................ 27
3.6.1 XPEDITOR.................................................................................................................................. 27
3.6.2 File-AID........................................................................................................................................ 27
3.6.3 File-AID IMS (FAIMS).................................................................................................................. 28
3.7 CONFIGURATION MANAGEMENT.................................................................................................... 29
3.7.1 Remedy....................................................................................................................................... 29
3.7.2 Endevor....................................................................................................................................... 29
3.7.2.1 FEATURES OF ENDEVOR...................................................................................................... 30
3.7.2.2 BENEFITS of ENDEVOR system............................................................................................. 30
3.7.2.3 Invoking ENDEVOR................................................................................................................. 31
3.7.2.4 ENDEVOR main menu............................................................................................................. 31
3.7.2.5 ENDEVOR Display Options Panel............................................................................................ 32
3.7.2.6 ENDEVOR Foreground Panel.................................................................................................. 32
3.7.2.7 ENDEVOR Background Panel.................................................................................................. 32
3.8 Application development libraries........................................................................................................ 33
3.8.1 PANVALET source objects.......................................................................................................... 33
3.8.2 PANVALET load module objects................................................................................................. 33
3.9 JCL Coding Standards......................................................................................................................... 34
3:10 Reference Link................................................................................................................................... 46

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 5 of 46

 Procedure’s & Guidelines

Preface

Purpose

This manual is intended as a reference document, which should be used to get an overview of the
Order Entry to Cash Systems of Pitney Bowes Inc. In addition it also aims to give a brief
introduction to the outsourcing project that is being carried out by WIPRO.

This is an evolving document. This document will be initiated and completed during the transition
phase. Nevertheless, since this document is intended for reference, there will be updates to this
document during the service phase as well.

Audience

This document is intended for the following audience:

 Those who would like to get an overview of the functional aspects of the Order to Cash
Systems.
 Any new team member who gets inducted into the team
 Those who start at off-shore facilities of Wipro on the project

Others, who are involved with the outsourcing project, could also use this document as a reference
document.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 6 of 46

 Procedure’s & Guidelines

Chapter 1 - Introduction

1.1 The Project

Pitney Bowes is a $4.1 billion global provider of integrated mail and document management
solutions. The company serves over 2 million businesses of all sizes in more than 130 countries
through dealer and direct operations. Has 4 business units – Document Messaging technologies,
Global mailing systems, Information based systems, Pitney Bowes Management Services. There
are several products and services included under Mail and Parcels, Production Mail, Financial
services, Outsourcing services, Professional services.

Pitney Bowes aims to leverage the business knowledge within its Order to Cash System by re-
deploying them towards development of strategic projects. In pursuance of this aim, Pitney Bowes
has decided to out source the maintenance of some of its existing applications and ongoing projects
to Wipro. Order to Cash is one such application selected for transition to Wipro.

Order to Cash (OTC) systems involves the processes that affect customers, from the time an order
is taken until receipt of payment. The system processes orders for the Pitney Bowes Global Mailing
Systems.

OTC includes 30 different applications. The major applications are Order Entry, Billing, Invoice
generator & Accounts receivables (A/R).

1.2 The Scope

For Order to Cash System, the following maintenance and enhancement activities should be carried
out:

Carry out Maintenance/Enhancements based on the Specs from Pitney Bowes team
Carry out the Production Support activities by providing On-Call support round the clock.
Change or add documents that support the system.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 7 of 46

 Procedure’s & Guidelines

Chapter 2 - Project Details

This chapter gives details of the phases for this outsourcing project, its technical environment, and
application summary.

2.1 Project Phases

The project is to transfer the responsibility of maintenance support of Order to Cash system from
Pitney Bowes to Wipro, which will be carried out in two phases namely:

 Transition Phase
 Service Phase

During the transition phase, the Wipro team will take over the responsibilities from Pitney Bowes
in various stages as per the plans detailed in Appendix A - Schedule of Activities for Transition, of
this document.

During the Service phase, Wipro will take full ownership of the systems and provide
maintenance support services from onsite as well as offshore.

2.2 Technical Environment

The Pitney Bowes system runs in the following environment:

Hardware Platform IBM – 3090

Operating System OS/390
Languages COBOL, EASYTRIEVE
Databases IMS-DB, DB2
Special Software JCL, FAIMS, SPUFI, FILE-AID, SORT,
IMS UTILITIES, Expeditor
Online Environment IMS DC
Configuration Management Endevor, Panvalet
Communication https:\\mymail.pb.com
Development/Test region TSOA, IMSTEST
Production region TSOA, IMSPROD

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 8 of 46

 Procedure’s & Guidelines

2.3 PB Development Environment

2.3.1 ISPF special Options

ISPF MAIN MENU

Menu, Utilities, Compilers, Options, Status, Help,

------------------------------------------------------------------------------
ISPF Primary Option Menu
Option ===>

0 Settings Terminal and user parameters User ID . : CX04347

1 View Display source data or listings Time. . . : 17:26
2 Edit Create or change source data Terminal. : 3278
3 Utilities Perform utility functions Screen. . : 1
4 Foreground Interactive language processing Language. : ENGLISH
5 COBOL/MVS Compile using COBOL for MVS 2.1 Appl ID . : ISR
6 Command Enter TSO or Workstation commands TSO logon : LOGDEV
7 Dialog Test Perform dialog testing TSO prefix : CX04347
8 System ID : 3090
9 XPEDITOR Test Environment MVS acct. : **NONE**
10 FA-IMS File-Aid IMS Release . : ISPF 5.0
11 XCOM File Transfer
E PBDE PB Devt Environment

Enter X to Terminate using log/list defaults

F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel

Option ‘E ‘ from ISPF main menu;

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 9 of 46

 Procedure’s & Guidelines

--------------------------- Pitney Bowes Development Environment ------------------------------

COMMAND ===>
-------------------------------------------------------------------------------------------------------------
( FPAC ) | ( FPAC )
1 PANV > PANVALET | 21 SCRP > Screen Plus Fac.
2 DB2 > DB2/QMF | 22 HSMUTIL > HSM Utilities
3 SPITAB > Spitab Util. | 23 DASD > Dataset Blocking
4 MSFG > MFS Generator | 24 CMP > Dataset Compress
5 PRTU > Print Util. | 25 MJCL > Model JCL
6 TURN > Turnover | 26 JSCN > JOBSCAN Facility
7 TRNS > TRANSFORM | 27 VPSP > VPSPRINT Utility
8 DBUTIL > Database Util | 28 VPS > VMCF Output Util.
9 MAD > M n D Sysytem | 29 OUT > Output Transfer
10 ENDEVOR > Version Cntl | 30 CSS > Compiler SubSystem
11 BOOK > BookManager | 31 GDG > Generate GDG's
12 FTEXP > FileTransfer | 32 DB2SPC > DB2 Table Spaces
13 FA > FileAid | 33 CAI2000 > Y2K Facility
14 ZEKE > JobScheduler | 34 CJRST > Class J Restore
15 XPED > Expeditor Fac. | 35 CBLMVS > Cobol for MVS & LE
|
|

--- Pitney Bowes Support System --- X = Terminate --- 17:35 ----- 03/04/15 --
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

OPTIO Function Description Remarks

N
1 Panvalet – User as version control Prod code can be copied to test
tool. Used to browse, edit, copy the environment and test code with
source code
permission can be moved to Prod.
2 DB2-QMF is used to access DB2 Can be accessed by logging onto
tables and run queries TSOC session.
3 SPITAB – used to access the SPITAB SPITAB tables are IMS tables which
IMS tables. are used to store edit/misc.
information.
4 MSFG – MFS Generator used to Used to generate the MFS screen
generate the MFS source codes source code. No longer working!!
6 TURN – Turnover is used to move For procedures to move different
source code and Load from types of programs, see the Migration
development to staging and procedures.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 10 of 46

 Procedure’s & Guidelines

production libraries.
7 TRNS – Transform Transform is the tool used to create
online screens and generate the
source code related to the Online
programs.
8 DB utilities used to access various
IMS DB tools
10 Endevor for version control Endevor is used only for JCLs &
documentation
12 FTEXP – File transfer utility
13 FA – File aid File access
14 ZEKE – Job scheduler to access the
scheduling information
15 Xpeditor for debugging Xpeditor is the de-bug tool.
23 DASD To estimate the DASD that has to be
allocated for datasets
30 & 35 CSS – Compiler sub system CBLMVS
– Used to compile the source code
31 GDG – create Generation datasets
34 CJRST – Class J restore To restore the archived Job logs

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 11 of 46

 Procedure’s & Guidelines

Option – 1 PANVALET

Pitney Bowes PANVALET Utilities

COMMAND ===>

PANVALET UTILITY SELECTIONS

( PAC )
1 = PAN > PANVALET
2 = PANDIR > PANVALET DIRECTORY LISTING UTILITY
3 = PANDELT > PANVALET MEMBER DELETE UTILITY
4 = PANXFER > PANVALET MEMBER TRANSFER UTILITY
5 = PANREST > PANVALET LIBRARY RESTORE UTILITY
6 = PCEZ > PANVELET COMPARE UTILITY for EASYTRIEVE
7 = PC > PANVALET COMPARE UTILITY for COBOL
8 = PANLSU > PANVALET LIBRARY SEARCH UTILITY
9 = PANMSU > PANVALET Member string search utility
10 = PANDXFM > PANVALET transform transaction delete
11 = PANAINA > PANVALET Inactivate PRODUCTION programs

F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE

F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Use Option-1 from this menu to browse, Edit or copy source code
Option –3 to delete source code member for a directory
Option –4 to transfer members across directories
Option – 5 to restore any panvalet library from the backups.
Option – 6 & 7 to compare source codes written in EZTRIEVE & COBOL
across directories
Option - 8 to search for a specific source code member across directories
Option - 9 to search for a string in source code present in a directory

Note :- The directory names used in development are DDPCN.TRNSFRM*.PANLIB ( ‘* ‘ is the

library id which can be ‘B’,’C’,’D’,’E’,’F’,’G’,’H’,’I’& ’J’) . Each group uses a different library id
in development region. Please use the id your group uses. The Staging directory name is
DDPCN.TRNSFRMA.PANLIB & the Production directory is PDPCN.TRNSFRMA.PANLIB

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 12 of 46

 Procedure’s & Guidelines

Option – 3 SPITAB

- SPITAB Utility Selection Menu -

COMMAND ===>

---------------------- Pitney Bowes SPITAB Utilities ------------------------

| |
| - SPITAB Selections - |
| |
| 1. Move a table between libraries |
| |
| 2. List the contents of a table |
| |
| 3. Print the COBOL copybook from a table |
| |
| 4. Data Center Processing |
| |
| |
| |
| |
| |
| |
| |
| |
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Use this option to access the SPITAB tables. It can be used to move the SPITAB table definition
between libraries and list the contents of a table . Alternatively, the data from the SPITAB tables
can be listed by logging into SPITAB on IMSTEST.

2.3.2 Compiling the source code

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 13 of 46

 Procedure’s & Guidelines

Programs can be compiled using the compiler subsystem which can be accessed by Option 5 from
ISPF main menu or Option 30 or 35 from the Pitney Bowes Development Environment panel.
The compilation panel looks as shown below:

- COBOL/MVS COMPILER SELECTION SUB-SYSTEM

This has to be Y if you- wantver
to 2.1.0
COMMAND ===> Want to Xpedite resubmit a program for
for debugging compilation
Re-Submit ORUU0169 Source ==> N ( Y or N )
XPEDITOR Req? ==> ( Y or N options 1, 5 and 8 only ) Mention
the
location of
1 IMS COMPILE/LINK Source input ==> PAN your
2 CICS COMPILE/LINK PDS - for a PDS dataset source
3 EZTRIEVE PAN - for a PANVALET Master File
4 DB2 BLANK - for options 7 and 8
5 COMPILE/LINK
6 COMPILE Only Compile Type ==>
7 LINK Only T - for TRANSFORM
8 TRANSFORM Rel 4.1 S - for TRANSFORM NAT. Subr.
9 Bat/IMS/C CPLINK

Be aware that compiles submitted by these panels use COBOL/MVS v2.1.

Any questions, call Paul Larsson 421 3639. Installed in June 2001.

-- Job Card Parameters -- Only JOB CLASS parm below works for TRANSFORM --
User ID ==> CX04347 1 ACCOUNT ==> DMIS
JOB CLASS ==> C MSGCLASS ==> X Program
ROUTE PRINT ==> R3 PROG ID ==> ORUU0109 name
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Use Option –1 for Programs with IMS (BMPs).

Option – 2 for CICS programs
Option – 3 for Eztrieve programs
Option – 4 for Programs with DB2
Option – 5 for plain batch COBOL programs (Compile and Link)
Option – 6 to generate only the compile listing
Option – 7 to generate the load module alone
Option – 8 to compile transform programs (Onlines)

After you fill in all the appropriate fields and select the option, hit enter to get to the next panel ,
which looks as shown below

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 14 of 46

 Procedure’s & Guidelines

COBPIPVS - IMS COBOL / MVS COMPILE DATA ENTRY MENU / PAN -

COMMAND ===>

Do not use quotes when entering data below:

Program name
You
Printer ID..................…………………….==> R661
can
PANVALET Source Member......………..==> use ORUU0169
your
Load PDS...................……………………==> Usually same as program
name
own
Load Member.................…………………==> ORUU0169
loadlib
Default IMS Loadlib........………………..==> DDPCN.IMSTEST.PGMLIB
TRANSFORM MULTI SYSTEM ID..... ==> H
Panvalet dev.
region where
source code exists
---------------------------------- Options ------------------------------------

Modify Compiler/Link Parms .......……. ==> N Enter Y or N

Subprogram or Main,...............……….. ==> M Enter S or M
Add or Change LKED SYSIN stmts ..… ==> N Enter Y or N
If your program
================== Compile/Link Options in Effect
is a =====================
called pgm,
COMPILE ==> this should be S
LINK ==>

After entering all the fields hit enter to submit the compilation job

How to look at Job spool?

 From ISPF main menu option 3.8 will take you to SDSF main menu.

From SDSF main menu

 Option ST to browse the status of jobs.
 Option DA to display the active jobs
 Option I to look at the Input queue
 Option O to look at the Output queue
 Option H to look at the Held output queue.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 15 of 46

 Procedure’s & Guidelines

You can also set filters from the pull down menu available on this panel to list only the jobs of
your interest.

Use the options in

this pull down
menu to set filters.

Note :- You will have to use the same SDSF utility to look at Production job spools too. You will
notice that the Production job logs are archived regularly on a daily basis. To look at the archived
job logs, use option 34 from the Pitney Bowes development Environment panel.

2.3.3 Dataset Information

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 16 of 46

 Procedure’s & Guidelines

PDPCN.PROD.JCL : Production Job dataset

PDPCN.DOC.CNTL : Production Job documentation

DDPCN.TSO.INCIDENT : Production Job incidents information

TDPCN.CALL.LIST(WHITE) : Production On call list

PDPCN.DBA.DCTNRY.* : Production DBD Source, pgm info & other details

PDPCN.TRNSFRMA.PANLIB : Production PANVALET SOURCE library

DDPCN.TRNSFRMA.PANLIB : System test PANVALET source library

DDPCN.TRNSFRM*.PANLIB
( ‘*’ = H or D or G or E or F or C…): Development PAVALET source library

DDPCN.USER.LOADLIB : Default development/test loadlib for Non-IMS

batch programs
DDPCN.IMSTEST.PGMLIB : Default development/test loadlib for IMS pgms

PDPCN.USER.LOADLIB : Production loadlib for Non-IMS batch programs

PDPCN.IMSPROD.LOADLIB : Production loadlib for IMS programs

TDPCN.RESTART.JCL : Dataset for restart JCL to get restarted ,any

production job that has abended.

2.3.4 Procedure to submit a Run request/on demand job:-

 Put the JCL in TDPCN.REQ.JCL with the correct naming convention.

 The naming convention for a run request job should be as below:-

a) The job name should be 8 characters long.
b) The first two characters should be ‘RR’
c) Third and fourth characters should identify the application to which the run request
job belongs to. (Viz. ‘OR’ for Order Entry, ‘ML’ for Meter licensing, ‘IG’ for Invoice
Generator etc)
d) The fifth , sixth and seventh characters should be the last three characters of your user
id.
e) The 8th character can be a ‘U’ if the job has any updates to datasets or databases.
Otherwise , it can be a ‘I’. with proper naming convention a job name should be like
say RROR338U

 Once the JCL is ready, JEM/JSCAN it for errors.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 17 of 46

 Procedure’s & Guidelines

 From ISPF, execute the command ‘RR’ to bring up the tool to submit a run request.
The panel looks as shown below:

Should be a Y if the
job is run for a prod
issue
No. of tapes used

Fill in all the required information in the above panel, put a ‘Y’ in the
“SECTION COMPLETE “ option and hit enter.

In the next two panels fill in the required information and the special instructions and hit enter to
submit the run request. A background job is submitted and you will be notified by a Run request
number once the submission is processed. Note down the RR number and get it approved by your
supervisor for the Run request to be processed by the Operations.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 18 of 46

 Procedure’s & Guidelines

Run Requests are required when:

1.) A one-time process is needed to meet a business need;

2.) A user is resolving an incident which cannot be programmatically fixed on a short term basis;
3.) A one time process for the 1st live run of a production job to test full volume data access and,
4.) A one time database Update to correct data corruption.

Run Requests continually are being misused. They are not intended to bypass the normal
application turnover process. The following standards are effective immediately.

1. Information Management is the central repository for all Run Request submissions. Canadian
personnel must sign onto Information Management directly and enter the appropriate
information. Mailing Systems users will continue to use the front end ISPF panel for entering
Run Requests.

2. The deadline for submission of Run Requests is 2:00 PM. Any Run Request received after
2:00 PM will not be processed until the next day unless it is in response to a production
incident. If in response to a incident, an Information Management problem record must be
entered in the Run Request record. A special field has been set up for this purpose. Data will
be verified by the Danbury Data Center before getting submitted. If the submission of the Run

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 19 of 46

 Procedure’s & Guidelines

Request will occur after 2:00 PM, the Data Center should be alerted prior to 2:00 PM to be on
the lookout.

3. All Run Requests will be printed by the Data Center at 2:00 PM and processed overnight. No
Run Requests will be processed during the day unless authorized by Data Center Management.

4. Run Requests will be processed at the end of the production schedule. The data center will
attempt to fix any Run Request using the same guidelines as production. Those Run Requests
where no call is requested will be left for the submitter to fix in the morning. Under no
circumstances will unsupported Run Requests from the night before be processed during the
following day. The submitter must fix the error and resubmit the Run Request to be scheduled
the next evening.

5. Project Manager's are accountable for using the Information Management system by 2:00 PM
and approve each Run Request for their area of responsibility. This can be done by entering
the free form text area of the record and putting a short comment indicating your approval.
This information is time and userid stamped so the Data Center can verify that the appropriate
approvals have been received.

6. Any Run Request which has a pre-requisite or dependency of a production job must be
supported. This includes all test schedules.

7. The job name for all Run Requests must take the following format both internally and
externally: RRXXBBBZ, where XX equates to the application being processed, BBB equates
to the submitters initials and Z equates to the run letter. The only exception to this rule is when
InfoPac (Canadian Report Management System) needs to be updated. In this case, the internal
job name must be production in order for the report to go out to InfoPac.

8. Any Run Request using over 100 cylinders of DASD space for any given dataset must receive
prior approval from the Storage Administration group, this includes SYSDA. Stargare
Administration contact personnel include: Ross Cook - 421-3407, Andy Switz - 421-3777 or
Jim Forrest - 421-3887.

9. Run Requests will not be processed during the freeze unless they are in response to a
production incident. The freeze schedule for the year can be found in dataset
DDPCN.USER.NEWS or in the Information Management database under the change
component of FREEZE.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 20 of 46

 Procedure’s & Guidelines

2.3.5 Doing a PSBGEN

From ISPF, submit the command ‘PSBGEN’ . The panel looks like as shown below

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 21 of 46

 Procedure’s & Guidelines

Enter the PSB name you want to Generate and hit enter to submit the request. A back ground job
will be submitted to process your request.

Note :- Please make sure that the PSB source is without any errors before you submit it for gen.

2.3.6 Migration of Source / Load to Stage & Production libraries

Once coded and tested to move the source code and load to the Stage and Production libraries,
follow the below procedure

NON IMS Batch programs

Execute command MIGU;1 to prepare the move for the source components to
DDPCN.TRNSFRMA.PANLIB. The panel looks as shown below:

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 22 of 46

 Procedure’s & Guidelines

Put a Y to
process the
data

This can be a N to
avoid too much
processing time

After submission, a source transfer request number is displayed on the screen. A JCL is generated
for a batch job submission in DDPCN.MIGRSYS.JCL.

To submit the batch job to migrate the components, go to option MIGU;2. The panel will display
the pending requests that need to be processed. Select the request number and hit enter to process
the source transfer request.
When source is migrated, it is also recompiled before the source and load are moved to Staging
libraries.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 23 of 46

 Procedure’s & Guidelines

2.4 Application Summary

The Order to Cash application is a group of different applications and is called OTC (Order to
Cash). It includes applications like Order Entry, Billing, Invoice Generator, Accounts Receivables
(A/R), General ledger, Sales reporting, Meter License etc. There are around 30 different
applications. The major applications (modules) are the Order Entry, Billing, Invoice generator &
Accounts receivables (A/R).
Using the Order Entry system the customer orders are entered into the system. The different ways
the Orders get into the system are through 1) Manually by Order Entry screens 2) Telephone
Ordering System 3) Small Office Division system.

Billing module (Periodic Billing or PEB) has several different sub-modules like Periodic
Equipment billing, Renewal Billing, One time billing or Initial Billing, EMA Billing, Renewal
EMA billing

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 24 of 46

 Procedure’s & Guidelines

Chapter 3 - Current Maintenance Process

Applications are changed based upon the creation of Change Requests (CRs) and scheduling of it in
a release or issuing a Ticket. The application changed is designed and program specifications are
written. Each program specification involves changing source code and creating production
deliverable. The programmer changes the source code, creates a deliverable and tests the changes.
At the end of each phase (specification, coding and testing) walkthroughs are conducted.

All work performed by any Pitney Bowes Order To Cash Team Member originates from one of
these four type-of-work areas.
 Processing Customer Changes through Change Request (CRs)
 Fixing Production Problems through Tickets.
 Developing and Maintaining Project Documentation through Document Change Request
(DCRs)
 Project Management

3.1 Change Request (CR)

The changes required for the Order To Cash (OTC) system are initiated using the Change Requests
(CRs).
There are three major steps involved in the CR process.

 CR Impact & Estimation

 CR Scheduling
 CR Implementation

3.1.1 CR Impact & Estimation

The first step in the CR process is to select the CR for impact analysis and estimation. If the
requirement is not clear then meeting will be arranged with the Project Manager. The Project
Manager will clarify the questions or he/she will discuss the questions with the client and the
answers will be forwarded to the group that raised the questions. The Project Manager will also
update the definition document of the CR if there is any change after discussing with the client and
notify the groups through the persons who attend the impact meeting. The groups will do the
estimate based on the new version of the CR.

3.1.2 CR Scheduling

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 25 of 46

 Procedure’s & Guidelines

The estimated CRs are picked up based on order of priorities, for discussion to prepare the
schedules. The purpose of these discussions is to arrive at an appropriate date by which the CR can
be implemented. The scheduling of CRs depends on the availability of resources and the CRs
priorities.

3.1.3 CR Implementation

For the selected CRs a high level design and a low level design will be prepared. After coding and
unit testing, the program will be turned over to system testing. There will be reviews conducted
after each of these activities. After system testing is successfully completed, the programs are
turned over to production on the release date.

3.2 Ticket
Ticket can be issued by anyone (including application programmers) when a production program
has problems being run or the output is incorrect.

Tickets are raised using REMEDY and normally do not have an associated documentations. If a
ticket is scheduled for a release, it must have tasks just like CR.

3.3 Application coding

The current source code to be modified is retrieved from the existing latest dataset
PDPCN.TRNSFRMA.PANLIB to the DDPCN.TRNSFRM*. PANLIB. The * varies from A to H.
depending on the application the source code should be moved to respective Panvalet library. Once
coding is complete, a code walkthrough must be held.

3.4 Pitney Bowes IBM coding standards

The Order To Cash (OTC) group has the following coding standard:

 Create a maintenance log in each csect (source module) being updated with the Project
Name, name of person who made the change, change date, release date and detailed description
of the change. Place the maintenance log at the end of the others so that the most current
maintenance log is last.
 Insert the date and name of the person when new lines are added/deleted from the Source
Code.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 26 of 46

 Procedure’s & Guidelines

3.5 Testing

3.5.1 Application Testing

After the coding is completed move the module in to the DDPCN.TRNSFRMA.PANLIB

development library and a code-walkthrough is held. Application testing is performed on each load
module that has changed. Component testing walkthroughs is done after component testing.

3.5.2 Component Testing

The application programmer must test the source changes made to the module to ensure that the
new code performs as per the requirements. This is component testing.

3.5.3 System Testing

The Application programmer must test the system to check if the changes made flows through the
system without any problems, gives the desired results and meets the user expectations.

3.6 Tools

3.6.1 XPEDITOR

XPEDITOR is the testing/debugging component for COBOL, PL/I, and Assembler programs in
TSO, MVS (batch), CICS and IMS environments. The supported features include program analysis
commands, execution control, intelligent breakpoints, Pseudo code with COBOL source update,
batch connect and changing data on the run. The supported databases include VSAM, IMS, DB2
and IDMS.

3.6.2 File-AID

File-AID is a general-purpose file and data manipulation tool for use in application development,
maintenance and production support activities. It runs under the dialog manager of ISPF and
operates similar to ISPF.

Features

File-AID aids in doing the following:

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 27 of 46

 Procedure’s & Guidelines

 Edit and browse data files in one of three modes: Formatted, which uses COBOL and PL/I
record layouts as templates over the data. - Vertical uses COBOL and PL/I record layouts. -
Character, displays the data as it would be seen in ISPF. Quickly and easily populate test
datasets on-line.
 Use existing COBOL and PL/I record layouts for data definition and manipulation.
 Use extensive file conversion and selection capabilities to eliminate the need to create “one-
time” file manipulation programs.
 Perform global “find and change” operations on all of the members of a partitioned dataset,
or just on those members you select.
 Allocate, delete and inquire about PDS and sequential files, as well as VSAM files,
alternate indices and paths on-line.
 Compare two datasets and create a report of the differences at the record or field level.
 Perform extensive data and file manipulation in batch mode.
 Also eliminates the ISPF restrictions on record length, dataset organization and file size.

For further information refer the File-AID feature manuals.

3.6.3 File-AID IMS (FAIMS)

File-AID for IMS is an interactive, full-screen system designed for the application development and
maintenance environment that enables you to edit, browse, extract, and load IMS data bases. File-
AID for IMS significantly reduces the time required creating and maintaining IMS test databases,
to view database information, and to perform production-troubleshooting activities.
The File-AID for IMS system consists of three products: File-AID for IMS/ISPF, File-AID for
IMS/DC, and File-AID for IMS/CICS.

 File-AID for IMS/ISPF runs as a dialog under TSO/ISPF and can access both on-line and
off-line IMS databases.
 File-AID for IMS/DC runs as a non-conversational MPP under IMS/DC.
 File-AID for IMS/CICS runs as a pseudo-conversational transaction under CICS and can
access IMS databases that is allocate on-line to CICS.

Key features of FAIMS

 Provides formatted full-screen displays to edit and browse databases.

 Allows data to be extracted from existing databases to build test databases.
 Automatically extracts data from IMS-defined and application-defined logically related
databases.
 Supports the loading of extracted data into either an existing database or an empty and not
initialized database.
 Provides access to all on-line or off-line IMS databases through TSO/ISPF. Optionally,
the File-AID for IMS/DC component can be used to access databases on-line to IMS/DC.
Similarly, you can use the CICS component to access on-line CICS databases.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 28 of 46

 Procedure’s & Guidelines

 Uses existing COBOL and PL/I segment layouts as templates to display data in the Browse,
Edit, and Selection functions. Layouts can also be used to enter data when in Edit and to data
print when in Browse or Edit.
 Uses existing DBDs to define the database structure.
 Supports retrieval of database dataset names defined to the RESLIB dataset through
Dynamic Allocation.
 Provides support for HDAM, HIDAM, HISAM, SHISAM, HSAM, Fast Path databases, and
secondary indexes.
 Supports extended functions such as reformatting databases with the companion product
File-AID/MVS.
 Provides an audit trail of all changes made during an edit session.
 Supports editing and browsing in secondary index sequence.
 Provides support for graphic characters through DBCS (Double-Byte Character Set)
support.
 Allows formatted printing of one or more database segments to SYSOUT or to a file.
 Provides a graphic hierarchy displays that shows segment relationships, current position,
and segment information.
For more information refer to File-AID for IMS 4.0 user manual.

3.7 CONFIGURATION MANAGEMENT

3.7.1 Remedy

Remedy is the standard tool that is being used by Pitney Bowes for the purpose of tracking and
managing the Tickets. It is the software where Tickets can be issued against a software/hardware
product like an application, or against an organization such as the service center. Remedy can be
accessed through https://pbremedy.pb.com/arsys.

Remedy provides the following high-level functions:

 The on-line opening, updating and closing of change requests for a given product.
 The on-line opening, updating and closing of PMR’s for a given product.
 An alert process which notifies designated individuals that a change request or trouble
report has been issued against a product that they are responsible for or associated with. The
notification messages can be viewed through PCRM and/or can be sent to user via E-mail.
 Reporting features, which provide listings of all change requests and problems, issued
against the products.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 29 of 46

 Procedure’s & Guidelines

3.7.2 Endevor

Endevor is a version control system

Overview

ENDEVOR TSO application setup

In order to use ENDEVOR, specific ISPF libraries must be allocated on NODETEST. The
ENDEVOR panels are not available on the production systems.
Application development libraries
Application libraries for all ENDEVOR source code, object libraries and load libraries are defined
on the NODETEST machine. Production only needs to process against the load module and
DBRM libraries. Production and the application programmers do use the JCL and copylibs for
system setup and debugging.

Software Development Life Cycle

ENDEVOR supports the software development life cycle. This cycle includes application
specification and coding, compiling & testing, release creation and application promotion to
production environment.

3.7.2.1 FEATURES OF ENDEVOR

Control Features

ENDEVOR establishes, maintains, and protects a control library of source programs, JCL, and
card-image data files.

Monitoring Features

ENDEVOR provides automatic monitoring of all source program development and maintenance
activity within its libraries.

Security Features

ENDEVOR has security features allowing users to restrict access to individual programs, and
allowing managers or administrators to restrict the use of any particular ENDEVOR facility.

Programmer Tool Features

ENDEVOR is a reliable and powerful programmer tool for creating, storing, and maintaining
source program code.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 30 of 46

 Procedure’s & Guidelines

3.7.2.2 BENEFITS of ENDEVOR system

ENDEVOR system solves the problems inherent in self-programmed systems. It does this by
providing direct communication between ISPF Edit and ENDEVOR library. The benefits of
ENDEVOR direct communication include:

 Ease of use.
 Use of ENDEVOR and ISPF without ENDEVOR/TSO as intermediary.
 Reduced overhead by bypassing the extra reading, writing, and DASD space required for
temporary data sets.
 Use of the full range of ENDEVOR and ISPF facilities.
 Display of standard ISPF error messages.
 Maintenance and display of ENDEVOR level stamps.
 Display of ENDEVOR user-comment records.
 Protection of production status or LOCKed ENDEVOR members.

3.7.2.3 Invoking ENDEVOR

ENDEVOR can be invoked from TSO command line by typing in ENDE and pressing <Enter>.

3.7.2.4 ENDEVOR main menu

The following options are available in the main menu:

0 DEFAULTS Specify ENDEVOR ISPF

default parameters
1 DISPLAY Perform Display functions
2 FOREGROUND Execute Foreground
Actions
3 BATCH Perform Batch Action
processing
4 PACKAGE Perform Foreground
Package processing

5 BATCH PACKAGE Perform Batch Package

SCL Generation

U USER MENU Display user option menu

T TUTORIAL Display information about

ENDEVOR
C CHANGES Display summary of
changes for this release

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 31 of 46

 Procedure’s & Guidelines

X EXIT Exit the ENDEVOR/MVS

dialog

3.7.2.5 ENDEVOR Display Options Panel

ENDEVOR Display Options Panel has the following features:

 Display element/component list information
 Display footprinted members and compressed listings
 Display site information
 Display stage information
 Display system definitions
 Display subsystem definitions
 Display type definitions
 Display processor group definitions
 Display approver groups
 Display inventory area/approver group relationships
 Display information about the current environment

3.7.2.6 ENDEVOR Foreground Panel

ENDEVOR Foreground Panel has the following features:

 Display an element
 Add or update an element into stage 1
 Retrieve or copy an element
 Execute the Generate Processor for this element
 Move an element to the next inventory location
 Delete an element
 Print elements, changes and detail change history
 Explicitly sign-in an element

3.7.2.7 ENDEVOR Background Panel

ENDEVOR Background Panel has the following features:

 Build batch SCL actions

 Edit request data set
 Submit job for batch processing
 Check request data set for syntax errors
 Enter additional JCL to be included with the job

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 32 of 46

 Procedure’s & Guidelines

For more information refer to ENDEVOR MVS USER MANUAL.

3.8 Application development libraries

The application development libraries hold source objects, load module objects and production
deliverables.

There are two types of libraries. The application test library, which is used by the application
programmer to change source code and then test the changes and the Panvalet, controlled
development/system test/production libraries, which holds the development/system test and
production source and deliverables.

3.8.1 PANVALET source objects

Application specification and coding involves creating source code, copylibs, dbrms, DB2 DDL
and other objects needed for an application.
Application programmers change source using Panvalet libraries that have the high level node as
‘DDPCN’.

Examples of some of the application libraries are:

PDPCN.TRNSFRMA.PANLIB Holds production COBOL, ASSEMBLER

and copylibs.
PDPCN.IMSPROD.DBDLIB Holds production DBD’s gen’d for
development
PDPCN.IMSPROD.DBDSRC Holds production DBD source code
DDPCN.TSO.INCIDENT Hold online/batch problems, abends &
their solutions
PDPCN.IMSPROD.PSBLIB Holds production PSB’s gen’d for
development
PDPCN.IMSPROD.PSBSRC Holds production PSB source code

Once the source code is changed, it may be tested from the DDPCN.TRNSFRMA.PANLIB library.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 33 of 46

 Procedure’s & Guidelines

3.8.2 PANVALET load module objects

PANVALET application test libraries

If source is being changed, the source is usually compiled into application test libraries. The
application library is are: PDPCN.USER.LOADLIB

3.9 JCL Coding Standards

JOB STATEMENT

Rules for card column alignment are as follows:

Operation JOB must begin in column 12.

Parameter list for JOB must begin in column 16.
Continuation of JOB statement must begin in column 16.

Job name must be the same as the PDS member name.

Job card format must be as follows: AANNNXFT

AA = Application identifier
(new application identifiers are defined by DCA)

NNN = Three digit job identifier defined by applications / Data Center Administration.

X = Job processing type, one of the following:

B: BMP (IMS Batch Message Processing, e.g. on-line)
H: File transfer
I: Image copy
N: No IMS database or DB2 access
O: Re-org
Q: QMF (DB2 batch)
R: Restore
T: SMU tape

F = Job execution frequency, one of the following:

D = Daily (Specify run days i.e.: Monday - Friday, Monday - Saturday, etc.
W: Weekly (Once a week)
B: Bi-monthly (Twice a month)
M: Monthly (Once a month)
Q: Quarterly (Every three months)
A: Annually (Once a year)

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 34 of 46

 Procedure’s & Guidelines

S: Special (Unique processing, i.e.: run on last 3 business days of month)

O: On request
T = Job type, one of the following:
I: Inquiry (or File Transfer SEND)
U: Update (or File Transfer RECEIVE)

JOB STATEMENT PARAMETERS

Account field must be PROD.

Programmer name field should specify a brief description of the job. A maximum length of 20
characters is allowed.

CLASS=

T for File Transfer jobs.

P for System A production. (IMSPROD)

9 for System C production. Examples include: DB2, CICS, SAS, Etc.

MSGCLASS = J for all production jobs

REGION = 5M (megabytes)

The following JOBLIBS are required:

PDPCN.USER.LOADLIB - When executing a non IMS batch program other than a system utility,
i.e., IEBGENER, IDCAMS, IEFBR14, etc.

PDPCN.MDC.LOAD1 - When executing a CICS Human Resource

application

PDPCN.MDFIN.LOADLIB - When executing a CICS financial application

An example of a job statement is as follows:

//AC005BDU JOB (PROD),'ACESS DAILY UPDATE',

// CLASS=P, MSGCLASS=J,
// REGION=5M

All remaining JOB STATEMENT parameters must be omitted, as they will default to Pitney
Bowes standards. Exceptions must be communicated to Data Center Administration.

EXEC STATEMENT:

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 35 of 46

 Procedure’s & Guidelines

Rules for card column alignment are as follows:

Operation EXEC must begin in column 12.

Continuation of EXEC statement must begin in column 16.

The step name must contain the first five characters of the job name, followed by three digits to
identify the step number, preferably in increments of 10.

The first two characters of the program name must match the application identifier.

If executing a PROC, use the available standard PROCS, i.e., SAS, BMCUPROC,
IMSPBMP, etc.

COND parameter coding, preferably COND=(0,NE), should be coded on all steps, except on the
first step and ZEKE STEPCHK, but may be tailored to the applications specific needs. The COND
parameter MUST NEVER be coded on the ZEKE STEPCHK unless authorized by Data Center
Administration.

ZEKE STEPCHK must be coded as the last step of the job in order to include it in our automated
scheduling package. Example:
.
//STEPCHK EXEC PGM=ZEKESET
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
SET ABEND IF HIGHCOND GT 0
//

In the above example, the job will abend if any step returns a condition code higher than 0.
Questions on ZEKE STEPCHK coding should be directed to the ZEKE schedulers in Operations.

THE JOBLIB statement must be used in lieu of STEPLIBS.

DD STATEMENT (DASD):

DSN=

Valid high level qualifiers are as follows:

PDPCV VSAM data sets

PDB2V DB2 data sets
PIMSN IMSPROD GSAM data sets
PIMSV IMSPROD data bases
SYS Assigned by Technical Services
PDPCN Production batch datasets

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 36 of 46

 Procedure’s & Guidelines

UDPCN File uploads (see section on UPLOAD files)

With the implementation of DFSMS (Data Facility Systems Managed Storage) - an additional
character has been added to the PDPCN high level qualifier to indicate the frequency that the
dataset is being created. This change enables the data center to perform DASD management more
efficiently by allowing migration of DASD datasets on a dataset level and not on a volume level.

Examples:

1. PDPCNT - Temporary files that go to SYSDA and are deleted at either end of job or at end of
step.

2. PDPCND - Files that are catalogued on PROD volumes on a daily basis and are used either
from job to job or from cycle to cycle.

The second node of the dataset must match the step name except for Database utilities. The
following apply for Database utilities:

Fastscan (HSSR) unload must have HSSR as the second node

Image Copies must have VAULT3X as the second node where

X = D for daily

= M for monthly

= W for weekly

= A for annual

The third node of the data set is up to the user, but should be meaningful, such as the datasets
ddname. For Database utilities, the third node must equal the job name while the fourth node must
equal the Database name. See examples below:

HSSR Unload: PDPCN.HSSR.OR015DDI.ADORDP0

Image Copy: PDPCN.VAULT3D.II905IDI.ADMVTY1

DISP= (NEW, CATLG, DELETE) for most dataset creations.

UNIT= SYSDA for datasets which are used only for the duration of the job. These datasets should
be deleted at the end of the job. Datasets larger than 100 cylinders must have an IDCAMS delete
statement immediately following the datasets last reference.

UNIT= PROD for data sets required by job(s) other than the creating job. Any data sets greater
than 500 cylinders must be approved by the Storage Administrator in Storage Administration.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 37 of 46

 Procedure’s & Guidelines

DCB= MDLDSCB must be the first parameter if creating a GDG dataset. Additional DCB info
may be coded as required.

COBOL BATCH / NATIVE / IMS PROGRAMS

Omit DCB information. You must specify BLOCK CONTAINS 0 RECORDS for the file. This
allows the system to determine the optimal block size for the dataset resulting in: 1.) Less DASD
space used, and 2.) Faster processing time.

EZTRIEVE PROGRAMS

Optimal block sizes must be specified.

SPACE= Allocation unit can be in tracks, cylinders or blocks.

EZTVFM datasets should be allocated in blocks using the following syntax: (see Appendix C for
additional details)

SPACE=(4096,(100,100))
Datasets up to 10 cylinders should be allocated in tracks. Example

SPACE= (TRK,(150,10),RLSE)

All other datasets must be allocated in cylinders.

The RLSE sub parameter must be coded unless a GSAM data set is being pre-allocated for IMS.

SYSOUT= When SYSOUT is required by a program, code SYSOUT=* under most situations.
NEVER code SYSOUT=X.

If printing at the Mailroom, the SYSOUT parameter must be coded as follows:

SYSOUT= (class, form name) where class is defined as follows for the Stamford Data Center
(SDC).

1 - Simplex
2 - Duplex
3 - Accounts Payable checks
4 - Quadruplex
6 - Special Forms
K - Payroll Checks
R - Payroll reports

SYSOUT=(class, form name) where class is defined as follows for the Mailroom.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 38 of 46

 Procedure’s & Guidelines

8 - Restricted class for confidential data

9 - General mailroom reports

SYSOUT=(class, form name) where class is defined as follows for RMDS reports.

V - RMDS class and form name is the RMDS report number

DEST= Rnnn, where nnn is the remote number.

DD STATEMENT (TAPE):

DSN= Valid high level qualifiers are as follows:

PDPCN - Production batch datasets

UDPCN - Production files transfer (see RACF administrator and see section on UPLOAD files)

The second node of the dataset must match the step name except for Database utilities. The
following apply for Database utilities:

Fastscan (HSSR) unload must have HSSR as the second node Image Copies must have VAULT3X
as the second node where

X = D for daily

= M for monthly

= W for weekly

= A for annual

The third node of the data set is up to the user, but should be meaningful, such as the datasets
ddname. For Database utilities, the third node must equal the job name while the fourth node must
equal the Database name. See examples below:

HSSR Unload: PDPCN.HSSR.OR015DDI.ADORDP0

Image Copy: PDPCN.VAULT3D.II905IDI.ADMVTY1

DISP= (NEW, CATLG, DELETE) for most dataset creations.

UNIT= TAPE36

For datasets larger than 500 cylinders unless DASD is authorized by the Storage Administrator in
Data Center Administration.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 39 of 46

 Procedure’s & Guidelines

For tapes leaving the Data Center and are absolutely guaranteed to be returned.

TAPE - For tapes which must be sent offsite, i.e., Credit Union, Microfiche etc. UNIT=TAPE
should only be used if Vendors cannot accept cartridges.

DCB= MDLDSCB must be the first parameter if creating a GDG dataset. Additional DCB info
may be coded as required.

LABEL= EXPDT=99000 must be coded when creating a GDG dataset. Multiple GDG files must
be stacked onto one tape and must be coded as follows:

LABEL=(n, SL, EXPDT=99000) where n is equal to the file number on the tape.

RETPD=60 days or less for non GDG datasets. Exceptions must approved and must be coded as
follows:

Only Standard label tapes (SL) are supported. Exceptions must be approved by the TLMS
specialist.

LABEL= (n, SL, RETPD=ddd) where n is equal to the file number on the tape and ddd is equal to
the number of days the dataset is to be retained.

Code VOL= (, RETAIN) for data sets that are used later in the same job.

Under no circumstances should a USER code EXPDT=99365 without prior approval from Data
Center Management. This parameter puts a permanent retention on the tape file.

An OFFSITE SHIPMENT FORM must be completed and sent to the Operations TLMS Specialist
in the Danbury Data Center to send a tape offsite.

Please refer to separate section on tape standards for additional details.

SYSTEM UTILITIES

IEBGENER: - IEBGENER requires only the following DD statements. Other DD statements will
not be allowed to be put into production.

SYSUT1 - defines input dataset(s).

SYSUT2 - defines output dataset.
SYSPRINT - IEBGENER message dataset
SYSIN - defines control statements
Code //SYSIN DD DUMMY unless reformatting output

Do not specify DCB information on output data set(s) unless the output is being reformatted.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 40 of 46

 Procedure’s & Guidelines

When creating a print file destined for RMDS, eliminate the IEBGENER step by writing the file
directly to RMDS via the user program.

IDCAMS: - If IDCAMS is used for the sole purpose of deleting datasets, replace IDCAMS with
PBSDR15. PBSDR15 will identify the amount of space used by a dataset before deletion takes
place. The data center and I/S can use this information to accurately identify the amount of DASD
required.

IDCAMS (PBSDR15) requires the following DD statements but others could be used

SYSPRINT - IDCAMS (PBSDR15) messages

SYSIN - Control statements

Specify LRECL and RECFM on the output dataset to allow the system to determine the optimal
block size.
Specify NOSCRATCH on the delete statement when deleting a tape dataset.

Always initialize a VSAM file with low values (HEX 0's). A high values record will cause
increased I/O's by inserting rather than adding, significantly adding to the job's runtime.

Omit CISIZE for batch files; VSAM will default to an optimal size.

SORT: - Only the following DD statements will be allowed in SORT steps.

SORTIN - defines input dataset(s).

SORTOUT - defines output dataset.
SYSOUT - sort message dataset.
SYSIN - defines control statements.

Do not code SORTWK data sets; SORT will dynamically allocate them for you.

Do not specify DCB for sort-out data set unless the file is being reformatted.

For input datasets on TAPE, specify estimated file size. (Estimated file size parameter does not
work for DASD datasets. SORT looks at the actual input to get the file size.)

Example 1 is the estimated file size parm on the EXEC statement

1) //STEPNAME EXEC PGM=SORT, PARM='FILSZ=E1500000' or

Example 2 is the estimated file size on the SYSIN statement

2) //SYSIN DD *
SORT FIELDS=(100,27,A)
OPTION FILSZ=E1500000

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 41 of 46

 Procedure’s & Guidelines

ICETOOL:-

This utility is used to combine multiple invocations of SORT or IEBGENER in one step.

See DFSORT Programming Application Guide release 11.1 and up for specific information.

IMS BMP PROCESSING:

Must invoke the IMSPBMP proc.

The program name and the PSB name must be the same.

If BMP is an update, it must take checkpoints and have checkpoint restartability. The checkpoint
frequency must be control card driven NOT program driven).

IMS BMP's and DB2 batch cannot co-exist in the same job. IMS BMP's run
on System A while DB2 batch runs on System C.

Use of DLI processing is prohibited, unless approved by DBA.

If a BMP is an inquiry with a PROCOPT=G it must take checkpoints. This is required because a
PROCOPT=G specifies read with integrity. Therefore, locks are held which tie up the PI
Enqueue/Dequeue pool. The checkpoint frequency must be control card driven not program
driven.

All trace statements such as exhibits and displays must be removed from application programs
before they are turned over to production.

When executing the IMSPBMP proc, the only DD statements allowed outside of the proc are as
follows:

GSAM data sets

Other application input or output data sets the checkpoint frequency DD statement

Use IEFBR14 to pre-allocate GSAM files. The DCB parameter must specify the LRECL, RECFM
and DSORG parameters. Omit the RLSE parameter.

Example: DCB=(LRECL=80,RECFM=FB,DSORG=PS)

DSORG=PS indicates the file is sequential and the system will optimize the block size
automatically.

Code the space parameter with RLSE in the step in which the GSAM file is written to.

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 42 of 46

 Procedure’s & Guidelines

Optimal block sizes must be specified for EZTRIEVE programs. Block size must be specified and
cannot exceed 12288 when destined for a laser printer.

APPLICATION PROGRAMS

COBOL: - Do not specify DCB information on non IMS output data set(s).

Code BLOCK CONTAINS 0 RECORDS allowing system determine optimal block size.

EZTRIEVE: - Specify optimal block size(s) on all output data set(s).

Use the = DASD Fast Path Access Code to determine the optimal block size.

DDNAME EZTVFM should be allocated SPACE= (4096, (100,100)) unless the file is written to.

I/O Counts - To determine the amount of space and I/O's processed by a dataset check the
following:

Look at the $SYSMSG dataset of your SDSF (3.8) output. Message IEF237I informs the User
what volume each DD is allocated to. Message ACTRT002 informs the User the number of I/O's
that went to each file.

An I/O, as shown in message ACTRT002 is the writing of 1 block of data. If you let SDB (System
Determined Block size) do the work, 2 I/O's equal 1 track of data because SDB uses half track
blocking as its optimal size.

For example: If the record size is 80 bytes, the optimal block size for a 3390 DASD device is
27,920. Since 1 track of a 3390 can hold more than 56,000 bytes, 2 blocks of 27,920 (27,920 X 2 =
55,840) can fit on one track. Consequently, 2 I/O's equal 1 track of data. Less I/O's means less
CPU time (see message IEF374I above) which means that your job runs faster. This equation is
true for most user written programs. Sort uses its own method of I/O called EXCP but gives you
the number of records and block size in its message dataset.

SMS Managed Data Sets

Development Data Set Migration Criteria Unit=TSO or:

DSNAMES listed below:

All datasets conforming to the standards will no longer require a UNIT parameter to be coded:

Userid.TSO....
DCOPuid.DCOP.... (copier only)
DDPCN.TSO....
DDPCN.DCOP.... (copier only)

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 43 of 46

 Procedure’s & Guidelines

DDPCND.... \
DDPCNW.... \ when getting ready to turn things over
DDPCNM.... \ to production, you can test using the
DDPCNQ.... \__production standards.
DDPCNA.... /
DDPCNB.... /
DDPCNS.... /
DDPCNO.... /

DDPCNT - Temp Sequential will be directed to SYSDA.

DIMSNT - Temp Sequential will be directed to SYSDA.
DDPCVT - Temp VSAM will be directed to SYSDA,
ALL other VSAM should remain DDPCV or DIMSV.

If standards are not followed and no unit parameter is coded, the datasets will be directed to
SYSDA and deleted current night (@19:45).

Any sequential datasets under SMS management that is used for backup purposes only will be
automatically directed to DFHSM ML2 for 425days.

Strictly backup data sets should have the following names:

*.*.BACKUP.* (3rd level of the DSN should be the word BACKUP)

Retention periods for datasets will be as follows:

Days On Days on Days on Management

Category of Data Set Primary Level 1 Level 2 class Name
Names DASD Inactive Inactive
Days Days

SYSDA Datasets Immediate 0 0 Temp

Userid. TSO 5 45 425 Standard
DCOP.uid.DCOP 5 45 425 Standard
DDPCN.TSO 5 45 425 Standard
DDPCN.DCOP 5 45 425 Standard
DDPCND 5 45 425 Standard
DDPCNW 5 45 425 Standard
DDPCNM 5 45 425 Standard
DDPCNQ 5 45 425 Standard
DDPCNA 5 45 425 Standard
DDPCNB 5 45 425 Standard
DDPCNS 5 45 425 Standard
DDPCNO 5 45 425 Standard
DDPCN.Endevor NOLIMIT NOLIMIT NOLIMIT NOMIG
DIMSV.CARES NOLIMIT NOLIMIT NOLIMIT NOMIG

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 44 of 46

 Procedure’s & Guidelines

DIMSV.IMSTEST NOLIMIT NOLIMIT NOLIMIT NOMIG

DIMSV.SPITABT NOLIMIT NOLIMIT NOLIMIT NOMIG
DIMSV.TRNSFRM NOLIMIT NOLIMIT NOLIMIT NOMIG

LAST HLQ

CNTL 25 100 425 TSOPERM

LOAD 25 100 425 TSOPERM
LOADLIB 25 100 425 TSOPERM
JCL 25 100 425 TSOPERM
PANLIB 25 100 425 TSOPERM
COBOL 25 100 425 TSOPERM
PROF 25 100 425 TSOPERM
MAILIN 25 100 425 TSOPERM
MAILOUT 25 100 425 TSOPERM

Until further notice, TSO datasets being created with UNIT=TAPExx specified will go to tape
regardless of the dataset name.

Production dataset migration Criteria:

Production temporary datasets (those going to Unit=SYSDA) must have a High Level Qualifier of:
PDPCNT or PIMSNT (Temporary GSAM)

(UNIT parameter is not required since SYSDA pool is SMS managed).

Datasets with the above HLQ get deleted after 3 days not referenced.

Production permanent DASD datasets (Those going to UNIT=PROD) must have a HLQ of (The
last character follows the job name standards for frequency). Unit parameter is not needed when
properly named.

Days On Days on Days on Management

Category of Data Set Primary Level 1 Level 2 class Name
Names DASD Inactive Inactive
Days Days

PDPCND 5 100 425 PRODQSTD

PDPCNW 5 100 425 PRODQSTD
PDPCNM 5 100 425 PRODQSTD
PDPCNQ 5 100 425 PRODQSTD
PDPCNA 5 100 425 PRODQSTD
PDPCNB 5 100 425 PRODQSTD
PDPCNS 5 100 425 PRODQSTD
PDPCNO 5 100 425 PRODQSTD

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 45 of 46

 Procedure’s & Guidelines

Development Database Data (CICS, IMS) VOLSER = DEVTxx

Days On Days on Days on

Category of Data Set Primary Level 1 Level 2
Names DASD Inactive Inactive
Days Days

DDPCV.CICSxxxx 7 100 425

DIMSV.IMSTEST 7 100 425

XXXX - Signifies the name of the region: i.e., TEST, PROD, etc.

3:10 Reference Link

Database services home page - http://dbantdbp1.ct.pb.com/dbservices/

PBI –IMS-Procedure & Guidelines Ver 1.2 Confidential Page 46 of 46