JAL: minor cleanup

2015-10-28T00:35:27Z

minor cleanup

Admin: 1 revision

2015-10-19T21:37:24Z

1 revision

← Older revision	Revision as of 21:37, 19 October 2015
(No difference)

JAL at 19:24, 16 October 2015

2015-10-16T19:24:29Z

New page

<var class="product">SirLib</var> stores a variety of change management information in the <var class="product">Model 204</var>
file SIRLIBD.
This data is used in the <var class="product">SirLib</var> 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.

<table class="thJustBold">
<tr class="head"><th>Field</th>
<th>Description</th></tr>

<tr><th>RECTYPE</th>
<td>Field indicating record type, with following values:
<table class="thJustBold">
<tr><th>SYS</th>
<td>Rectype that specifies system defaults for <var class="product">SirLib</var>. There is only one record with this RECTYPE.</td></tr>

<tr><th>FIL</th>
<td>Rectype that specifies file defaults for <var class="product">SirLib</var> (missing fields on this record means use system default). One record of this RECTYPE for each registered file.</td></tr>

<tr><th>PRO</th>
<td>Unused.</td></tr>

<tr><th>USR</th>
<td>Rectype for user security definition.</td></tr>

<tr><th>DOC</th>
<td>Documentation associated with a project.</td></tr>

<tr><th>CHG</th>
<td>Project Identifier record.</td></tr>

<tr><th>PRC</th>
<td>Procedure record for procedures checked out by programmers.</td></tr>

<tr><th>HST</th>
<td>Historical information kept if "Keep History" is specified in file or system defaults.</td></tr>
</table></td></tr>

<tr><th>CHANGE</th>
<td>Project name in CONTROL.<file>.</td></tr>

<tr><th>FILE</th>
<td>Name of managed update file.</td></tr>

<tr><th>FFILE</th>
<td>Name of update procedure file.</td></tr>

<tr><th>PROC</th>
<td>Procedure name.</td></tr>

<tr><th>PROJECT</th>
<td>Unused.</td></tr>

<tr><th>RESOURCE</th>
<td>Name of a protected resource, as follows:

<table class="thJustBold">
<tr><th>CHANGE</th>
<td>Access to Change Definition.</td></tr>

<tr><th>CONFIG</th>
<td>Access to Re-Configuration.</td></tr>

<tr><th>CUT</th>
<td>Access to File Cutover.</td></tr>

<tr><th>RESEQ</th>
<td>Access to Procedure Resequencing -- <var>Z</var> prefix command in <var class="product">SirPro</var>.</td></tr>

<tr><th>SECURE</th>
<td>Access to File-specific security.</td></tr>
</table></td></tr>

<tr><th>USER</th>
<td>User ID (from $ACCT).</td></tr>

<tr><th>WFILE</th>
<td>Work File. File that procedures were moved to via one of the managed update commands.</td></tr>

<tr><th>ACTIVITY</th>
<td>The managed update activity tracked on a history record (RECTYPE = HST).</td></tr>

<tr><th>ADMIN</th>
<td>Administrator id specified on the SYS rectype.</td></tr>

<tr><th>EXEMPT</th>
<td>Prefix of procedures not to be stamped with internal comments on the status of the application of changes. Maximum length is forty characters.</td></tr>

<tr><th>DATE</th>
<td>General date/time stamp, in YYYYMMDDHHMM form.</td></tr>

<tr><th>HISTORY</th>
<td>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.</td></tr>

<tr><th>OVERWRITE</th>
<td>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.</td></tr>

<tr><th>PROC.LOCK</th>
<td>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.</td></tr>

<tr><th>REQ.IDENT</th>
<td>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.</td></tr>

<tr><th>SECURE</th>
<td>Single character flag indicating whether the SECURITY settings defined in Option 4 of the <var class="product">SirLib</var> 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.</td></tr>

<tr><th>STAMP</th>
<td>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.</td></tr>

<tr><th>TEXT</th>
<td>Text for change comments and documentation on RECTYPE=DOC. Maximum length is 72 characters.</td></tr>

<tr><th>TIME</th>
<td>Time stamp, in HHMM form.</td></tr>

<tr><th>CUT.BASE</th>
<td>Date/Time stamp from the most recent cutover of BASE procedures (RECTYPE=FIL), in YYYYMMDDHHMM form. When BASE procedures are cutover they are deleted.</td></tr>

<tr><th>CUT.CHANGE</th>
<td>Date/Time stamp for the last time Update procedures were cutover (RECTYPE=FIL), in YYYYMMDDHHMM form. When Update procedures are cutover they are deleted.</td></tr>

<tr><th>CUT.IDENT</th>
<td>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.</td></tr>

<tr><th>CUT.STAMP</th>
<td>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.</td></tr>

<tr><th>FIRST.CUT</th>
<td>Date/Time stamp for the first cutover performed on a file (RECTYPE=FIL), in YYYYMMDDHHMM form.</td></tr>

<tr><th>LAST.CUT</th>
<td>Date/Time stamp for the last time Cutover performed on a file (RECTYPE=FIL), in YYYYMMDDHHMM form.</td></tr>

<tr><th>LAST.CONF</th>
<td>Date/Time stamp for the last time a file was reconfigured (RECTYPE=FIL), in YYYYMMDDHHMM form.</td></tr>

<tr><th>UNLOCK</th>
<td>Date/Time stamp when a procedure was checked back in by an updating programmer (RECTYPE = PRC), in YYYYMMDDHHMM form.</td></tr>
</table>

==See also==
{{Template: SirLib topic list}}

[[Category: SirLib]]

SIRLIBD record structure - Revision history

JAL: minor cleanup

Admin: 1 revision

JAL at 19:24, 16 October 2015