ZSS Application Conventions

ZSS Systems

ZSS systems are indicated by either a three character numeric code or a three character mnuemonic. The following are applicable to our environment:

System Files

File DDNames for a ZSS system generally begin with the same letter as programs for that system. Master files generally have a particular format, namely xyFILE. The first character, x follows normal conventions for ZSS system naming. The second character, y, usually indicates the function of the file. This is followed by the word FILE. The file function is system dependent.

Examples:

FSFILE

The Subsidiary Ledger master file that is part of the Financial Records System.

BDFILE

The Detail master file that is part of the Billing/Receivables subsystem of the Student Information System.

EPFILE

The Position Control master file that is part of the Human Resources System.

Cobol Copy Members

A common naming convention is used for record descriptions for all master files. The first character is the system. The second character is a C, indicating that it is a copy member. The third and fourth characters are the same as the first two characters of the master file DDName. The last two characters are RC. Thus FCFGRC is the copy member for the FGFILE in FRS.

Easytrieve Plus Libraries

As with Cobol copy members, Easytrieve Plus library members have a common name structure. The format is LIBxxxyy where xxx is the system or subsystem and yy are the first two characters of the master file DDName. For example, LIBPRSPO is the POFILE library for the Purchasing subsystem (PRS) of FRS. One feature of Easytrieve Plus libraries is that the DBD element number of a variable is included as a comment on the same line as the Easytrieve Plus definition.

Other files are similar, but without the FILE ending. Some examples are probably best.

FPOPFL

The first character indicates this is part of the FRS system. The second character in FRS indicates the subsystem, in this case, the Purchasing subsystem. The next two characters, OP, indicate the file function, in this case the old purge file, which happens to be a generation data group of archived purchasing documents.

NLACFL

The first character indicates this is part of the LMS system. This system has no subsystems, so uses L as a second character. The next two characters, AC, indicate this is the FRS Accrual Feed file, which happens to be a generation data group.

SINLFL

The first character indicates this is part of the Financial Aid Management subsystem of the Student Information System. Most FAM files of this type use I as the second character. The next two characters, NL, show this to be the LMS disbursements feed, the NL matching the scheme used above to indicate an LMS file.

General

As can be seen from the preceeding items, each system and subsystem may use its own format. It would be nice to see the same conventions used throughout, but, unfortunately, this does not hold. It is fairly easy to get a grasp on these names by using the SPX M.1 option for a particular file prefix (e.g., AUP07.FAM.PROD for FAM files).

ZSS System Transactions

Most ZSS systems permit updating through batch transactions. This is the preferred method of updating through batch programs. The actual layout of the batch transactions is described under the ZSS DBD Training section. Each transaction has an Easytrieve Plus library describing its record format with a name in LIBxxyyy format. xx is an abbreviation of the system or subsystem. yyy is the three character batch identifier. For example, LIBSI50C is the 50C transaction for the SIS system, which is a transfer credit maintenance transaction.

OIT Applications Support

Last Modified: Tuesday, 28-Nov-2000 11:03:29 CST

©1999 All Rights Reserved