Messages BBXSAFPA through BBXSAFPZ

BBXSAFPA

BBSEC contains more statements than will fit in buffer area. Read terminated.

Explanation: The BBSEC member contained too many statements. BBXSAF00 will attempt to use what was read from the member.

User response: The read buffer allows approximately 1,000 statements. Reduce the number of unnecessary lines in the member.

BBXSAFPB

Last statement indicates continuation, but no subsequent parameter found.

Explanation: The last non-comment entry processed in the BBSEC member indicated a continuation by ending in a comma, but no subsequent non-comment statement was found before reaching the end of the member. BBXSAF00 will terminate processing of the member with no update of the security information.

User response: Correct the incorrect continuation and rerun the BBXSAF00 job.

BBXSAFPC

No TYPE=SYSPROG statement found.

Explanation: No parameter statement with TYPE=RESOLVE or TYPE=SYSPROG as the first parameter was found in the BBSEC member. SAF security is not implemented in this environment.

User response: Place a parameter statement with TYPE=SYSPROG as the first parameter in BBSEC member if SAF security is desired.

BBXSAFPD

Errors encountered while parsing parameters

Explanation: While processing a REFRESH request to BBXSAF00, errors were found in the TYPE=RESOLVE parameter statement. See messages BBXSAFP2 and BBXSAFP3. The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Correct errors and resubmit REFRESH request.

BBXSAFPE

USECNNM value is invalid. Valid values are 'YES' and 'NO'

Explanation: The value specified for the USECNNM parameter was neither YES nor NO. (Y and N are also acceptable.) The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Correct errors and resubmit REFRESH request.

BBXSAFPF

DEFAULT TAKEN FOR KEYWORD keyword

Explanation: A keyword in the TYPE=RESOLVE parameter statement was found in error. The default for this keyword will be taken when the SAF control block (SAFCB) is built as part of BBXS initialization.

User response: Respecify the keyword value in the TYPE=RESOLVE parameter statement, unless you want to use the default.

BBXSAFPG

Not 'TYPE=SYSPROG', parameter statement bypassed

Explanation: A parameter statement was encountered in the BBSEC member that is not for TYPE=RESOLVE. This statement is bypassed.

User response: If SAF security is desired, place the TYPE=RESOLVE statement in the BBSEC member. Verify that TYPE=RESOLVE is spelled correctly and is the first statement listed.

BBXSAFPH

Only YES or NO is valid for keyword keyword

Explanation: An invalid value was entered for the indicated keyword. Only a value of YES or NO is allowed.

The default will be taken if the SAF control block is built as part of BBXS initialization.

User response: Specify a value of YES for the indicated keyword, unless you want to use the default value.

BBXSAFPI

Only ALLOW or FAIL is valid for keyword ERRPROC

Explanation: An invalid value was entered for keyword ERRPROC. Only a value of ALLOW or FAIL is allowed. The FAIL default is used if the SAF control block is built as part of BBXS initialization.

User response: Specify a value of ALLOW for keyword ERRPROC, unless you want to use the default value.

BBXSAFPJ

cannot find the BBCT for Subsystem subsystem

Explanation: A valid BBCT control block could not be located for the indicated Subsystem as specified in the BBXSAF00 PARM field, This could indicate that BBXS initialization is in progress, and the SAF control block will be completed as part of the indicated BBX Subsystem's initialization. SAF security is not implemented in this environment.

User response: Wait and retry the REFRESH function later. If this message is still issued, or is issued at the original BBXS initialization, contact BMC Support. If attempting to refresh the security definitions for an alternate BBX Subsystem, make sure that it has been created and initialized.

BBXSAFPK

SAFCB Create/Refresh already in progress

Explanation: The ENQ, ENQSAFCB:REFRESH is currently held, indicating that the refresh or build of the SAF control block is in progress. The current request to update the SAF control block is terminated.

User response: Wait and retry the REFRESH later if necessary. This can indicate an attempt to refresh the SAFCB while BBXS initialization is taking place. If the ENQ is never released, contact BMC Support.

BBXSAFPL

Only ENABLE and DISABLE are valid for keyword ACTION

Explanation: The ACTION parameter only takes values of ENABLE or DISABLE. The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Respecify the keyword value in the ACTION parameter unless you want to use the default.

BBXSAFPM

Only SMF and CVT are valid for keyword SYSID

Explanation: The SYSID parameter only takes values of SMF or CVT. The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Respecify the keyword value in the SYSID parameter unless you want to use the default.

BBXSAFPN

Only YES, NO, or ALL are valid for keyword PRIVATE

Explanation: The PRIVATE parameter only takes values of YES, NO, or ALL. The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Respecify the keyword value in the PRIVATE parameter unless you want to use the default.

BBXSAFPO

Initialization parameters are missing

Explanation: No initial parameters were passed to BBXSAF00. If running as a batch job or JCL, the EXEC statement must contain a PARM= parameter containing either SCAN or REFRESH. The execution of BBXSAF00 is terminated.

User response: If this message is issued as part of BBXS initialization, contact BMC Support. Otherwise, correct the batch job so it passes the PARM=parameter containing either SCAN or REFRESH.

BBXSAFPP

Initialization parameters are incorrect

Explanation: The initial parameters passed to BBXSAF00 are incorrect. If running as a batch job or started task, the EXEC statement PARM=parameter must contain either SCAN or REFRESH. The execution of BBXSAF00 is terminated.

User response: If this message is issued as part of BBXS initialization, contact BMC Support. Otherwise, correct the batch job so it passes the PARM=parameter containing either SCAN or REFRESH.

BBXSAFPQ

BBXSAF00 Must be executed from an APF-authorized library

Explanation: BBXSAF00 must be executed from an APF-authorized library. The execution of BBXSAF00 is terminated.

User response: Execute BBXSAF00 from an APF-authorized library.

BBXSAFPR

'TYPE'= PARAMETER MUST BE FIRST PARM CODED, PARAMETER STMT BYPASSED

Explanation: A statement was found in the BBSEC member that does not have TYPE=as the first parameter. This statement is bypassed.

User response: If SAF security is desired, make sure TYPE=RESOLVE or TYPE=SYSPROG is the first parameter statement in the BBSEC member. A possible source of this error is leaving off a comma after a parameter when there are following parameter for the same security definition. The lack of the comma indicates the end of the security definition and the next parameter statement is treated as the start of a new security definition. As this next parameter is not a "TYPE=" parameter, this message is issued.

BBXSAFPS

Only SYSPROG and BBX are valid for keyword AUDMSG

Explanation: The AUDMSG parameter only takes values of SYSPROG or BBX. The SAF control block (SAFCB) is not refreshed, and security checking continues with the existing SAFCB.

User response: Respecify the keyword value in the AUDMSG parameter unless you want to use the existing value.

BBXSAFPT

Scan processing complete

Explanation: SCAN processing for the BBSEC member has completed. BBXSAF00 terminates normally.

User response: Examine the SAFCRPT DD output for results of SCAN processing.

BBXSAFPU

Previous 'TYPE=SYSPROG' statement found, this parameter stmt bypassed

Explanation: Only the first occurrence of the TYPE=SYSPROG or TYPE=RESOLVE parameter statement is processed. All subsequent parameter statements containing TYPE=RESOLVE or TYPE=SYSPROG are bypassed. The security definitions are updated using the first TYPE=SYSPROG definition.

User response: Remove any extra TYPE=SYSPROG parameter statements from the BBSEC member.

BBXSAFPW

SAF Security changes complete and enabled

Explanation: The BBSEC TYPE=SYSPROG definition has been processed and the SAF Security Table for SYSPROG Services has been updated. BXSAF00 terminates normally.

User response: No action is required.

BBXSAFPX

SAF Security has been disabled

Explanation: Because ACTION=DISABLE has been specified in the TYPE=SYSPROG definition, of the BBSEC member, the Security for SYSPROG Services has been disabled. BBXSAF00 terminates normally.

User response: Running with SYSPROG Security disabled should be limited to emergency situations.

BBXSAFPY

SYSPROG Services product not installed. No security established

Explanation: During BBX Subsystem initialization, SYSPROG Service has not been detected. The BBSEC member in the Logical PARMLIB is scanned only and no update will be made to the SYSPROG Services security table.

User response: None, unless SYSPROG Services has been installed. Check to make sure that SYSPROG Services exists in the same load library as the BBX Subsystem load modules.

BBXSAFPZ

SAF Security remains unchanged

Explanation: An error was encountered while processing the BBSEC member. Other messages should describe the errors. BBXSAF00 terminates without updating the SYSPROG Security definitions.

User response: Review the BBXSAF00 output and correct an indicated errors.