- Description:
- This check will compare z/OS® UNIX System Services current system
settings with those specified in the BPXPRMxx parmlib members used
during initialization and issue an exception message if a difference
is found. For PARM values on the MOUNT statement, the check is case
sensitive, detecting and raising an exception for otherwise identical
values that are expressed in different cases.
Note
that if a dynamic symbolic is contained in the value specification
for any BPXPRMxx statement, that statement may be flagged as changed
because the current dynamic value is different from the value that
was used when the BPXPRMXX statement was originally processed.
If the system finds syntax errors in one or more of the
BPXPRMxx parmlib members the check issues message BPXH046E. If syntax
errors are found, the check does not make a comparison between the
system and the parmlib settings. You must correct all syntax errors
before the check will compare the system and the parmlib settings.
See the explanation for message BPXH046E in z/OS MVS System Messages, Vol 3 (ASB-BPX) for
more information.
The z/OS UNIX dynamic settings that will
be checked are:
z/OS UNIX dynamic
settings checked |
|
---|
AUTHPGMLIST
AUTOCVT
FILESYSTYPE
FORKCOPY
IPCSEMNIDS
IPCSEMNOPS
IPCSEMNSEMS
IPCMSGNIDS
IPCMSGQBYTES
IPCMSGQMNUM
IPCSHMMPAGES
IPCSHMNIDS
IPCSHMNSEGS
IPCSHMSPAGES
LIMMSG
LOSTMSG
MAXASSIZE
MAXCORESIZE
MAXCPUTIME
MAXFILEPROC
MAXFILESIZE
MAXMMAPAREA MAXPIPEUSER
|
MAXPROCSYS
MAXPROCUSER
MAXPTYS
MAXQUEUEDSIGS
MAXSHAREPAGES
MAXUIDS
MAXUSERMOUNTSYS
MAXUSERMOUNTUSER
MOUNT FILESYSTEM
NETWORK
NONEMPTYMOUNTPT
PRIORITYGOAL
PRIORITYPG
ROOT FILESYSTEM
SHRLIBMAXPAGES
SHRLIBRGNSIZE
STEPLIBLIST
SUPERUSER
SYSCALL_COUNTS
TTYGROUP
USERIDALIASTABLE
VERSION
|
- For the FILESYSTYPE statement, the types specified in the BPXPRMxx
parmlib members will be compared to what Physical File Systems are
currently running.
- For the ROOT/MOUNT FILESYSTEM statements, the following will be
checked:
- Mount point
- Mode, RDWR for example.
- Automove setting. Note that AUTOMOVE and system list are both
treated as AUTOMOVE.
- PARM subparameter
- For the NETWORK statement, only the MAXSOCKETS value will be
checked for AF_INET and AF_INET6.
- Reason for check:
- When dynamic changes are made to z/OS UNIX, the BPXPRMxx parmlib members
should be updated with the changes so that they will be available
the next time z/OS UNIX is initialized.
- z/OS releases the check
applies to:
- z/OS V1R9 and later.
- User override of IBM® values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
UPDATE
CHECK(IBMUSS,USS_PARMLIB)
SEVERITY(LOW) INTERVAL(01:00) DATE('date_of_the_change')
REASON('Your reason for making the update.')
- Debug support:
- No
- Verbose support:
- No
- Parameters accepted:
- No
- Reference:
- See:
- Messages:
- This check issues the following exception messages:
See the BPXH messages in z/OS MVS System Messages, Vol 3 (ASB-BPX).
- SECLABEL recommended for multilevel security users:
- SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for
information on using SECLABELs.
Output:
CHECK(IBMUSS,USS_PARMLIB)
START TIME: 03/29/2006 16:09:05.512021
CHECK DATE: 20060112 CHECK SEVERITY: LOW
BPXH003I z/OS UNIX System Services was initialized using OMVS=(DD,DN),
where each 2-character item is a BPXPRMxx suffix.
BPXH041I The following differences were found between the system
settings and the BPXPRMxx parmlib concatenation:
Option BPXPRMxx Value System Value
-----------------------------------------------------------
MAXFILEPROC 256 111
MAXPTYS 256 255
MAXCPUTIME 1000 999
Physical File Systems not in parmlib
-----------------------------------------------------------
AUTOMNT
Changed File Systems
-----------------------------------------------------------
File System: ZOS18.ETC.HFS
BPXPRMxx Value:
Path: etc
Automove: AUTOMOVE
Access: RDWR
Parm: NONE
System Value:
Path: etc
Automove: AUTOMOVE
Access: READ
Parm: NONE
File System: MYHFS
BPXPRMxx Value:
Path: /jkad
Automove: AUTOMOVE
Access: RDWR
Parm: NONE
System Value:
This file system is currently not mounted.
* Low Severity Exception *
BPXH040E One or more differences were found between the system settings
and the settings in the current BPXPRMxx parmlib concatenation.
Explanation: Check USS_PARMLIB detected changes made to either the
system settings or to the BPXPRMxx parmlib members.
System Action: The system continues processing.
Operator Response: Report this problem to the system programmer.
System Programmer Response: View the message buffer for information
on what values have changed. Use the DISPLAY OMVS,OPTIONS command
to view what the current system settings are. The system values can
be changed dynamically by using the SETOMVS command. If the current
system values are desired, then a permanent definition should be
created so the values will be available the next time z/OS UNIX
System Services is initialized. A permanent definition can be
created by editing the BPXPRMxx parmlib members to include the
desired values.
Problem Determination: See BPXH041I in the message buffer.
Source: z/OS UNIX System Services
Reference Documentation: See MVS System Command Reference in z/OS
MVS System Commands for information on using the DISPLAY
OMVS,OPTIONS command. See MVS System Command Reference in z/OS MVS
System Commands and Managing operations, section: Dynamically
changing the BPXPRMxx parameter values in z/OS UNIX System Services
Planning for information on using the SETOMVS command. See
Customizing z/OS UNIX in z/OS UNIX System Services Planning and
BPXPRMxx in z/OS MVS Initialization and Tuning Reference for
information on editing the BPXPRMxx parmlib members.
Automation: N/A
Check Reason: Reconfiguration settings should be kept in a permanent
location so they are available the next time z/OS UNIX is
initialized.