SIRLIBD record structure

SirLib stores a variety of change management information in the Model 204 file SIRLIBD. This data is used in the SirLib reporting system (Option 6 from the main menu) and may also be processed by user-provided reporting programs. This appendix explains the record layout for SIRLIBD.

Field	Description
RECTYPE	Field indicating record type, with following values: SYS Rectype that specifies system defaults for SirLib. There is only one record with this RECTYPE. FIL Rectype that specifies file defaults for SirLib (missing fields on this record means use system default). One record of this RECTYPE for each registered file. PRO Unused. USR Rectype for user security definition. DOC Documentation associated with a project. CHG Project Identifier record. PRC Procedure record for procedures checked out by programmers. HST Historical information kept if "Keep History" is specified in file or system defaults.
CHANGE	Project name in CONTROL.<file>.
FILE	Name of managed update file.
FFILE	Name of update procedure file.
PROC	Procedure name.
PROJECT	Unused.
RESOURCE	Name of a protected resource, as follows: CHANGE Access to Change Definition. CONFIG Access to Re-Configuration. CUT Access to File Cutover. RESEQ Access to Procedure Resequencing -- Z prefix command in SirPro. SECURE Access to File-specific security.
USER	User ID (from $ACCT).
WFILE	Work File. File that procedures were moved to via one of the managed update commands.
ACTIVITY	The managed update activity tracked on a history record (RECTYPE = HST).
ADMIN	Administrator id specified on the SYS rectype.
EXEMPT	Prefix of procedures not to be stamped with internal comments on the status of the application of changes. Maximum length is forty characters.
DATE	General date/time stamp, in YYYYMMDDHHMM form.
HISTORY	Single character flag indicating whether historical information should be kept for a file or system. Contains either blank, Y (yes) or N (no). If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank means keep history.
OVERWRITE	Single character flag indicating whether programmers are allowed to overwrite each other's update procedures (overwriting one's own update procedure is always allowed, though a switch on the XCOMPARE screen will help prevent accidental overwrites). Contains either a blank, Y (yes) or N (no). If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank means allow overwriting.
PROC.LOCK	Single character flag indicating whether procedures should be locked against managed updates once a developer has checked out the procedure (checkout occurs when a "Q" command is executed against the procedure). Contains a blank, Y (yes) or N (no). If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank means don't lock procedures.
REQ.IDENT	Single character flag indicating whether an existing project identifier is required for generating update procedures. Contains a blank, Y (yes) or N (no). If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank means don't require identifiers.
SECURE	Single character flag indicating whether the SECURITY settings defined in Option 4 of the SirLib main screen should be enforced. Contains a blank, Y (yes) or N (no). If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank means don't secure.
STAMP	Single character flag indicating whether managed procedures should be stamped with a single line comment for each change that has been applied. If RECTYPE=FIL, blank means refer to the setting on RECTYPE=SYS. If RECTYPE=SYS, blank indicates that stamping should be done.
TEXT	Text for change comments and documentation on RECTYPE=DOC. Maximum length is 72 characters.
TIME	Time stamp, in HHMM form.
CUT.BASE	Date/Time stamp from the most recent cutover of BASE procedures (RECTYPE=FIL), in YYYYMMDDHHMM form. When BASE procedures are cutover they are deleted.
CUT.CHANGE	Date/Time stamp for the last time Update procedures were cutover (RECTYPE=FIL), in YYYYMMDDHHMM form. When Update procedures are cutover they are deleted.
CUT.IDENT	Date/Time stamp for the last time Project Identifiers were cutover (RECTYPE=FIL), in YYYYMMDDHHMM form. Project Identifiers are deleted from the "CONTROL.filename" file when they are cutover.
CUT.STAMP	Date/Time stamp for the last time internal procedure stamps were cutover, that is, removed from procedures in the file (RECTYPE=FIL), in YYYYMMDDHHMM form.
FIRST.CUT	Date/Time stamp for the first cutover performed on a file (RECTYPE=FIL), in YYYYMMDDHHMM form.
LAST.CUT	Date/Time stamp for the last time Cutover performed on a file (RECTYPE=FIL), in YYYYMMDDHHMM form.
LAST.CONF	Date/Time stamp for the last time a file was reconfigured (RECTYPE=FIL), in YYYYMMDDHHMM form.
UNLOCK	Date/Time stamp when a procedure was checked back in by an updating programmer (RECTYPE = PRC), in YYYYMMDDHHMM form.

See also

• SirLib
• SirLib implementation
• SirLib programmer's reference
• SirLib update example
• SirLib change control
• SirLib security
• SirLib reports
• SirLib configuration options
• SirLib problem resolution
• SIRLIBD record structure
• SirLib "getting started" steps
• SirLib date processing