Crear una “Comisión permanente de seguimiento de la accesibilidad” Dicha Comisión de creó a finales del año 2008 y es integrada por

The first four words (0 through 3) of every logical log entry contain the information shown in the table “First Four Log Entry Words Version 1 Format.” Note that the record group description is found in Word 0 of every physical log record as well as in Word 0 of the logical log entry.

Information might be lost or misrepresented if SDASUPPORT is forced to return log data in the old format (version 0). When a program calls LOG_GET or LOG_READ and the conversion routines detect that an upper limit in the old style headers has been exceeded the following warning message is issued:

The SUMLOG file contains records using the header format that has resulted in misrepresented information returned using the old header format. LOG_GET_ENTRY or LOG_READ_RECORD should be used to retrieve SUMLOG data.

Writing Log Analysis Programs

Version 1 header values that are misrepresented when they are translated to version 0 headers include the following:

• The actual log entry length exceeds 1,023 words. A warning is NOT generated for these entries because this limit is already exceeded with existing log entries. The length of the log entry in words (word 3.[41.10]) is set to 1,023.

• The number of physical records in the entry exceeds 255. A warning is generated for these entries and the total number of physical records in the entry (word 0.[39:08]) is set to 255.

• The mix number exceeds 65,535. A warning is generated for those entries and the mix number (word 0.[15:16]) is set to 0 (zero).

• The job number exceeds 65,535. A warning is generated for these entries and the job number (word 0.[31.16]) is set to 0 (zero).

Table 2–1. First Four Log Entry Words Version 0 Format

Word Field Value Description

0 Record group description

[47:08] The cardinality of this record within the logical log entry (“this is record m of n”) beginning with 1 [39:08] The total number of physical records in this logical log

entry

[31:16] The JOBNUMBER value of the process that caused the log entry

[15:16] The MIXNUMBER value of the process that caused the log entry

1 Julian date in binary. Obtain the Julian date in the form YYYYDDD by adding 1,900,000 to the number found in this word.

2 Time of day, in units of 2.4 microseconds 3 Log entry type code

[47:06] Length of fixed part of entry in words

[41:10] Length of the entire log entry in words, unless all the bits are on (value equal to 1023), in which case the entry is longer than 1022 words.

[31:02] Result indicator (Always present in Security Log. Present in SUMLOG only when the Secure Accountability Facility (SAF) is licensed.) 0 Successful actions that are not security relevant 1 A Security Log corresponds to this SUMLOG.

In the first record in a SUMLOG, a 1 in this field means that a Security Log was created when this SUMLOG was created.

Table 2–1. First Four Log Entry Words Version 0 Format

Word Field Value Description

2 Successful actions that are security relevant, including SETSTATUS entries requiring security administrator privilege; use of the ??SECAD primitive; security attribute assignments (volume and

directory); attachment of guardfiles to files; USERDATA changes; BOJ and BOT of privileged programs, security administrator privilege programs and tasking programs; LOGON of privileged users and security administrators.

3 Failed actions that are security violations, including general security violations and MCS security violations

[29:02] Record visibility (Always present in Security Log. Present in SUMLOG only when the Secure Accountability Facility (SAF) is licensed.) 0 Unspecified

1 Public–maintenance and halt/load records 2 Private–records that are not public or secured 3 Secured–MCS security violations

[27:12] Major type. This value gives a general indication of the type of log entry.

[15:16] Minor type. This value indicates the specific log entry type. Note that minor type values are unique only within a given major type. For a list of log types, refer to the table “Log Entry Classes.”

Table 2–2. First Four Log Entry Words Version 1 Format

Word Field Value Description

0 [47:02] The SUMLOG header version (value = 1) [45:01] <reserved>

[44:05] _{The number of valid words in the last}

record including header words. The

computation to calculate the total number of words in the entry is as follows: w0.[44:05] + (29 * (w0.[31:16] - 1))

[39:08] New format SUMLOG header indicator (value = 0) [31:16] The total number of physical records in this logical log

entry

[15:16] The cardinality of this record within the logical log entry (“this is record m of n”) beginning with 1

Writing Log Analysis Programs

Table 2–2. First Four Log Entry Words Version 1 Format

Word Field Value Description

1 [47:12] Major type. This value gives a general indication of this type of log entry.

[35:16] Minor type. This value indicates the specific entry type.

Note: Minor type values are unique only within a

given major type.

[19:01] Record truncated. If this field is 1, the record is incomplete.

[18:01] <reserved>

[17:18] Julian date in binary. Obtain the Julian date in the form YYYYDDD by adding 1,900,000 to the number found in this word.

2 [47:02] Result indicator (Always present in Security Log. Present in SUMLOG only when the Secure Accountability Facility (SAF) is licensed.)

1 In the first record of a SUMLOG, this value indicates that a Security Log was created along with this SUMLOG.

In records other than the first, this field has the meanings shown in the following text.

0 Successful actions that are not related to security 1 Failed actions that are not related to security 2 Successful actions that are related to security,

including SETSTATUS entries requiring security administrator privilege; use of the ??SECAD primitive; security attribute assignments (volume and

directory); attachment of guard files to files; USERDATA changes; BOJ and BOT of privileged programs, security administrator privilege programs, and tasking programs; and logging on of privileged users and security administrators.

3 Failed actions that are security violations, including general security violations and MCS security violations

[45:02] Record visibility (Always present in Security Log. Present in SUMLOG only when the Secure Accountability Facility (SAF) is licensed.) 0 Unspecified

1 Public-maintenance and halt/load records 2 Private records that are not public or secured 3 Secured-MCS security violations

[43:08] Length of fixed part of entry in words [35:36] Time of day, in units of 2.4 microseconds

Table 2–2. First Four Log Entry Words Version 1 Format

Word Field Value Description

3 [47:24] The JOBNUMBER value of the process that caused the log entry.

[23:24] The MIXNUMBER value of the process that caused the log entry