Chapter 10

 

Section 1 - Natural Naming Standards

 

Format: AANNXZZZ

Where: AANN Is the system name (reference Chapter 6, paragraph titled System Name)
X Is the program type, where:

Previously used program names Version 1.2 Applications

2  Batch Program
3  On-line Program
6  Batch ADAMINT and Natural Extensions
7  On-line ADAMINT and Natural Extensions
8  On-line Maps

  Version 2 Only

A  Parameter Data
B  Batch Program
C  Copy Code (Include)
D  Program Description
F  Batch Map
G  Global Data Area
H  Help Routine
J  Jobstream
L  Local Data Areas
M  On-line Map
N  Sub-program
P  On-line Program
Q  Help Map
S  Sub-routine
T  Help Map (Text)
X  JCL Procedure Step name
Z  Recording

ZZZ Is the numeric program number within the system.  The program number will be 000 for the start-up program for the system.  The start-up program will be entered in the NATURAL Security profile for each on-line production library.  The program number for all other programs will be in increments of 10.  If more than 99 modules are created within a system, the first character for subsequent modules will be alphabetic.

Example: AANNX010, AANNX020...AANNX990, AANNXA00, AANNXA10...)

 

Programs that perform common functions are to be documented and stored in a separate area.  The appropriate system identifiers assigned to these sharable areas are to be defined and so labeled within the PCREGISTER.  The libraries containing the programs will be documented in PREDICT and will be assigned a unique keyword which will facilitate reporting on their availability.  The application development groups will approve the inclusion of documentation, maintenance, and publication of the libraries used for this purpose.


10.1.1  Library Names 

NATURAL libraries contain all of the programs for an application.  NATURAL security is used to control authorizations for the programs and files used within an application.
 

Format: AANNZZZZ

Where: AANN Is the system name (reference Chapter 6, paragraph titled System Name)

ZZZZ Is the library suffix identifier.  The following are the commonly assigned library suffixes:

TPRD      On-line Production
BPRD      Batch Production
UQRY      On-line user ad hoc/query
UPRD      User Batch overnight reporting (large reports)
TTST      On-line Development
BTST      Batch Development
USER      User Daytime Batch Processing

 

In some cases, security, user base, complexity or cross system integration may require the splitting of applications of the same type within the same system.  The naming convention for accomplishing this is to substitute an incremental number starting with 2 for all additions after the first. 

Example: AANNTPRD is the first library, AANNTPR2 is the second library, and AANNTPR3 is the third library.


10.1.2  Default Application Profiles for Natural Security 

System DB00 has been established for defining default applications of each type.  Each default application has profile and control limits estab­lished with appropriate capabilities for each library type.  All new applica­tions will copy and rename default applications to the applicable system from the appropriate default library.  Modifications to the settings of the various Flag and Value settings used in these Libraries should not be performed after the proper library type has been copied.   The values provide many different control features that have been established as beneficial throughout our implementation procedures of many products.  Expansion of the default limits are allowed only with written approval from Database personnel on an individ­ual system basis.

 

 

Home Up 10.1 Naming Standards 10.2 Program Structure 10.3 Processing Rules 10.4 Data Base Fields 10.5 Define Data 10.6 Initialization 10.7 Batch 10.8 System Construction 10.9 Tables 10.10 Maps 10.11 Help 10.12 Error Processing 10.13 Natural Security 10.14 Predict Support 10.15 Audit 10.16 HOC Programming 10.17 Construct Standard