z/os v1r4.0 unix system services planning
TRANSCRIPT
z/OS V1R4.0 UNIX System Services PlanningVTAM TCP/IP
SNA Network
SNA Network
TN3270-C TN3270-S rlogin-C rlogin-S telnet-C telnet-S
TN3270-C TN3270-S rlogin-C rlogin-S telnet-C telnet-S
-- TELNET 3270 Client -- TELNET 3270 Server -- rlogin Client -- rlogin Server -- telnet Client (not shown) -- telnet Server
-- TELNET 3270 Client -- TELNET 3270 Server -- rlogin Client -- rlogin Server -- telnet Client (not shown) -- telnet Server
TN3270-S
lpp
Active before
Attributes of directory jane as long as OMVS.JANE.HFS is mounted
inode of directory /
F FF
Figure
13.
Direct
mount
276
z/OS
V1R4.0
UNIX
System
Services
Planning
Using
direct
mount
The
root
file
system
should
be
set
up
so
that
it
does
not
require
frequent
changes
or
updates
(outside
of
SMP/E
maintenance).
To
achieve
this
we
will
allocate
an
intermediate
HFS
data
set
called
OMVS.USERS
and
mount
it
at
/u.
All
user
directories
that
are
added
will
reside
in
this
new
HFS
data
set
and
not
in
the
root
HFS
data
set.
Sample
JCL
to
allocate
this
intermediate
HFS
is
in
Figure
15.
Change
the
JCL
to
fit
your
environment.
The
next
thing
to
do
is
mount
this
new
intermediate
HFS
data
set
at
/u.
The
mount
can
be
performed
from
an
ID
that
has
superuser
authority
by:
v
Using
the
usr/sbin/mount
REXX
exec
from
the
shell
v
Using
the
TSO
MOUNT
command
v
Using
the
mount
shell
command
D
F FF
AUTOMOUNT FACILITY
FFF FF
user1, user2, userx..
(Automount Facility will dynamically allocate pseudo directories to act as mount points and mount HFS
data sets only when files are accessed)
Figure
14.
Automount
facility
//STEP01
EXEC
lpp
The
file
system
data
space,
SYSZBPX2,
is
useful
if
the
hang
condition
appears
to
be
due
to
a
file
system
latch.
For
more
information
on
the
DUMP
command,
particularly
on
specifying
a
large
number
of
operands,
see
z/OS
MVS
System
Commands.
Reviewing
dump
completion
information
After
the
dump
completes,
you
receive
an
IEA911E
message
indicating
whether
the
dump
was
complete
or
partial.
If
it
was
partial,
check
the
SDRSN
value.
If
insufficient
disk
space
is
the
reason,
delete
the
dump,
allocate
a
larger
dump
data
set,
and
request
the
dump
again.
Recovering
from
a
failure
The
operator
needs
to
recover
if
a
failure
occurs:
v
Kernel
failure:
As
a
result,
interactive
processing
in
the
shell
and
z/OS
UNIX
applications
fail.
v
File
system
type
failure:
z/OS
UNIX
continues
processing
even
though
the
file
system
type
is
not
operational.
Requests
to
use
the
files
in
any
file
systems
of
that
file
system
type
will
fail.
v
File
system
failure:
As
a
result,
some
files
cannot
be
used,
which
may
cause
programs
to
fail.
The
operator
starts
recovery
by
collecting
messages
and
a
dump,
if
written.
z/OS
UNIX
system
failure
If
the
z/OS
UNIX
system
fails,
the
operator
collects
problem
data,
which
includes
messages,
SVC
dumps,
and
SYS1.LOGREC
records
for
abends
and
decides
if
re-IPL
is
warranted.
The
work
in
progress
when
the
failure
occurred
is
lost
and
must
be
started
from
the
beginning.
File
system
type
failure
After
a
failure
of
a
file
system
type,
the
system
issues
message
BPXF014D.
In
response,
the
operator
or
automation
corrects
the
problem
as
indicated
by
previous
messages
and
then
enters
R
in
reply
to
message
BPXF014D.
File
system
failure
These
events
can
be
symptoms
of
file
system
failure:
v
0F4
abend
v
EMVSPFSFILE
return
code
v
EMVSPFSPERM
return
code
412
z/OS
V1R4.0
UNIX
System
Services
Planning
v
A
file
becomes
unrecognizable
or
unopenable
After
a
failure
of
a
file
system,
the
operator:
1.
Restores
the
HFS
data
set
with
the
data
set
from
the
previous
level.
For
more
information
on
recovering
an
HFS
data
set,
see:
v
z/OS
DFSMS
Migration
v
z/OS
DFSMShsm
Storage
Administration
Guide
2.
Asks
a
superuser
to
logically
mount
the
restored
HFS
data
set
with
a
TSO/E
MOUNT
command.
3.
Notifies
all
shell
users
that
when
they
invoke
the
shell
they
will
mount
a
back-level
file
system,
telling
them
the
mount
point.
(Use
the
wall
command
to
broadcast
a
message
to
all
shell
users.)
Files
added
since
the
back-level
data
set
was
saved
must
be
re-created
and
added
again.
If
the
physical
file
system
owning
the
root
fails,
or
if
the
root
file
system
is
unmounted,
the
operator
must
restore
the
root
file
system.
This
can
be
done
by
a
superuser
who
is
defined
with
a
home
directory
of
//SYSUT1
DD
/*
/*
/*
File System OMVS.ETC
TCPIP2TCPIP1 TCPIP3 TCPIP4CTC/ IUTSAMEH
Dissatisfied
Overall
How
satisfied
are
you
that
the
information
in
this
book
is:
Very
Dissatisfied
Easy
to
Easy
to
Well
Applicable
to
your
Please
tell
us
how
we
can
improve
this
book:
Thank
you
for
your
responses.
May
we
contact
you?
h
Yes
h
No
When
you
send
comments
to
IBM,
you
grant
IBM
a
nonexclusive
right
to
use
or
distribute
your
comments
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Name
Address
Company
or
Organization
Phone
No.
Readers’
Comments
Softcopy publications
IBM Systems Center publications
z/OS UNIX porting information
z/OS UNIX support
Workload Manager (WLM)
Time Sharing Options Extensions (TSO/E)
z/OS Communications Services (TCP/IP Services)
ISPF
Hardware considerations
Workstation connections
What you can do with z/OS UNIX System Services Application Services
Application programmers
Chapter 2. Migration overview
Developing a migration strategy
Actions required for all migrations
Installing books for the OHELP command
Creating separate HFS data sets for /etc, /dev, /tmp, and /var
Updating configuration files
Changing file attributes for certain utilities and the UUCP function
Command differences due to symbolic links
Updating security procedures
OS/390 V1R10 or z/OS UNIX V1R1 to z/OS UNIX V1R4
OS/390 UNIX V2R9 to z/OS UNIX V1R4
OS/390 UNIX V2R8 to z/OS UNIX V1R3
OS/390 UNIX V2R7 to z/OS UNIX V1R4
OS/390 UNIX V2R6 to z/OS UNIX V1R4
Chapter 4. z/OS UNIX Version 1 Release 4 overview
Release summary
Automove system list
Enhanced program security
Enhanced pthread support
Process start/end exits
zFS enhancements
Release summary
ISHELL enhancements
msys for Setup for z/OS UNIX
Shutting down z/OS UNIX without re-IPLing
Starting colony address space outside of JES
Unmounting file systems that leave the sysplex
Chapter 6. z/OS UNIX Version 1 Release 2 overview
Release summary
Preventing applications from being interrupted by signals
pread and pwrite enhancements
Release summary
Binary semaphore support
Large file support
Long long support
Monitoring BPXPRMxx values
pthread affinity service
Skulker shell script
Release summary
BPXPRMxx syntax checker
Shared library extended attribute
Release summary
Magic number
Release summary
inetd and rlogind daemons
UNIXMAP class
Release summary
BPXPRMxx
Overview
Establishing an /etc file system for a new release
Chapter 14. Customizing z/OS UNIX
Overview
Setting up kernel services
Evaluating virtual storage needs
Reducing the amount of ESQA needed to support servers
Prioritizing kernel work on your system
Running in goal mode
Defining classification rules as needed
Defining BPXPRMxx parmlib members in IEASYSxx
Customizing the BPXPRMxx parmlib members
Defining file systems
CTnBPXxx parmlib member to control tracing
IEADMR00 parmlib member to gather dump data
SMFPRMxx parmlib member to specify timeouts
Customizing the OMVS cataloged procedure to run the kernel initialization program
Running a physical file system in a colony address space
How to start colonies
Running a temporary file system in a colony address space
Enabling certain TSO/E commands to z/OS UNIX users
Setting up the REXX parameter modules
Checking for setup errors
Overview
What is a z/OS UNIX customization task?
Preparing to use msys for Setup
Using msys for Setup for z/OS UNIX customization
Chapter 16. Establishing UNIX security
Overview
Setting up users and groups
Activating supplemental groups
Security implications of programs running in the HFS
Authority checks
Obtaining security information for a group
Obtaining security information for a user
Setting up field-level access for the OMVS segment of a user profile
Defining group identifiers (GIDs)
Defining user identifiers (UIDs)
Setting user limits
Assigning UIDs and GIDs in an NFS network
Assigning identifiers for users and groups
Upper limits for GIDs and UIDs
Creating z/OS UNIX groups
Assigning superuser attributes
Using UNIXPRIV class profiles
Allowing z/OS UNIX users to change file ownerships
Using the CHOWN.UNRESTRICTED profile
Using the SUPERUSER.FILESYS.CHOWN profile
Steps for setting up BPX.SUPERUSER
Deleting superuser authority
Changing a superuser from UID(0) to a unique nonzero UID
Steps for changing a superuser from UID(0) to a unique nonzero UID
Switching in and out of superuser authority
Assigning a UID of 0
Setting up the BPX.* FACILITY class profiles
Security requirements for ServerPac and CBPDO installation
If you use uppercase group and user IDs
If you use mixed-case group and user IDs
If you have problems with names such as UUCP, UUCPG, and TTY
Defining cataloged procedures to RACF
Controlling access to files and directories
Setting classes for a user's process
Using the FILE.GROUPOWNER.SETGID profile
Changing the owner or group for a file
Creating a set-user-ID or set-group-ID executable file
Protecting data
Using access control lists (ACLs)
ACLs and ACL entries
How ACLs are used in file access checks
Auditing changes to ACLs
Auditing access to files and directories
Specifying file audit options
Steps for creating a sanction list
Steps for activating the sanction list
Maintaining the security level of the system
Steps for maintaining the security level of the system
Defining the OMVSAPPL profile for the APPL class
Setting up TCP/IP security
Overview
Using the Network File System (NFS)
Creating a hierarchical file system
Using uppercase and lowercase letters in filenames and pathnames
Allocating an HFS data set for the root file system
Defining the root file system
What happens when file systems are mounted?
Steps in mounting file systems
Restrictions on mounting file systems
Managing file systems
Removing unnecessary files from directories
Improving accesses to file systems
Unmounting file systems
Deciding how to mount your root HFS for execution
Leaving the root HFS mounted in read/write mode
Post-installation actions for mounting the root HFS in read-only mode
Mounting the root HFS in read-only mode
Customizing cron, uucp, and mail utilities for a read-only root HFS
Customizing the cron and uucp utilities
Customizing the mail utility
Copying the file system
Ways to back up HFS data sets
DFSMShsm
Using direct mount
Naming specific directories using the automount facility
Changing which data sets get automounted
Stopping the automount facility
System console file
Recovering from file system problems with the root
Installing service into the HFS
Example of installing service
Transporting the HFS from the driving system to the target system
Installing service into /etc
Chapter 18. Using the zSeries file system (zFS)
Overview
When would you want to use zFS?
zFS and shared sysplex
Overview
How the end user views the HFS
Summary of new HFS data sets
Comparing file systems in single system pre-OS/390 UNIX V2R9 and OS/390 UNIX V2R9 or later environments
File systems in single system pre-OS/390 UNIX V2R9 Environments
File systems in single system OS/390 UNIX V2R9 or later environments
File systems in OS/390 UNIX V2R9 or later sysplex environments
Procedures for establishing shared HFS in a sysplex
Steps in creating the sysplex root HFS data set
Steps in creating the system-specific HFS data sets
Steps in mounting the version HFS
Using the automove system list (SYSLIST)
Steps in creating an OMVS couple data set (CDS)
Steps in updating COUPLExx to define the OMVS CDS to XCF
Customizing BPXPRMxx for shared HFS
Sysplex scenarios showing shared HFS capability
Scenario 1: First system in the sysplex
Scenario 2: Multiple systems in the sysplex – using the same release level
Scenario 3: Multiple systems in a sysplex using different release levels
Keeping automount policies consistent on all systems in the sysplex
Steps in keeping your automount policy consistent on all systems
Moving file systems in a sysplex
Shared HFS implications during system failures and recovery
Shared HFS implications during a planned shutdown of z/OS UNIX
State of file systems after shutdown
File system initialization
Using distributed BRLM
Steps for setting up distributed BRLM on every system in the sysplex
Mounting file systems using NFS client mounts
File system availability
Read-write connections for sysplex-aware file systems
Read-only connections for non-sysplex aware file systems
Read-only connections for sysplex-aware file systems
Situations that can interrupt availability
Tuning z/OS UNIX performance in a sysplex
DFS considerations
Overview
By system programmer action
By TSO/E user action
Supplying an alternative shell
For the z/OS shell
For the tcsh Shell
Customizing files for the z/OS shell
Customizing /etc/profile
Customizing $HOME/.profile
Customizing /etc/init.options
Customizing /etc/rc
Customizing /etc/csh.login
Customizing /etc/csh.cshrc
Customizing /etc/complete.tcsh
Enabling utilities
Enabling the man pages
Customizing c89, cc, and c++ (cxx) compilers
Using the built-in c89/cc/c++ utility for the z/OS shell
Using non-default high-level qualifiers
Selecting C/C++ compilers
Setting up c89 to work with the current C/C++ compiler
Targeting an OS/390 release earlier than the current one
Targeting an earlier release
Customizing the terminfo database
Re-creating the terminfo database
For the z/OS shell
For the tcsh shell
Chapter 21. Customizing for your national code page in the shell
Overview
Steps for setting up your national code page
Customizing for Japanese and Simplified Chinese
Steps for customizing the login file for the z/OS shell
Steps for customizing the login file for the tcsh shell
Steps for displaying messages
TSO/E messages
PROFILE PLANGUAGE and the OMVS command
Chapter 22. Configuring the UNIX-to-UNIX copy program (UUCP)
Overview
Custom applications
Add an entry to the permissions file
Define the group ID and the user ID to RACF
If you use uppercase IDs
If you use mixed-case group and user IDs
If you have problems with using NUUPC
Configuring communication with remote systems
Obtain information about remote systems
Create or edit configuration files
Editing a configuration file
Compile the configuration files
Schedule periodic UUCP transfers with cron
Creating a crontab entry
Testing the connection
Contacting the remote site
Displaying information about recorded UUCP events
Notifying remote systems about password changes
Chapter 23. Using Enhanced ASCII functionality
Overview
Chapter 24. Managing operations
Terminating threads
Planned shutdowns using F BPXOINIT,SHUTDOWN=...
Steps for shutting down z/OS UNIX using F BPXOINIT,SHUTDOWN=...
Partial shutdowns (for JES2 maintenance)
Steps for partial shutdowns for JES2 maintenance
File system shutdown
What F OMVS,SHUTDOWN does
Dynamically changing the BPXPRMxx parameter values
Steps for dynamically changing certain BPXPRMxx parameter values
MAXPROCSYS
MAXPTYS
Activating the HFS file system for the first time
Activating a single sockets file system for the first time
Activating multiple sockets file systems for the first time with Common INET
Steps for increasing the MAXSOCKETS value
Adding another sockets file system to an existing Common INET configuration
Tracing events in z/OS UNIX
Steps for tracing events in z/OS UNIX
Steps for tracing DFSMS/MVS events
Steps for re-creating problems for IBM service
Displaying the status of the kernel
Steps for displaying the status of the kernel
Steps for displaying the status of BPXPRMxx parmlib limits
Taking a dump of the kernel and user processes
Steps for displaying the kernel address space
Steps for displaying process information
Steps for displaying global resource information
Steps for preallocating a sufficiently large dump data set
Steps for taking the dump
Reviewing dump completion information
Recovering from a failure
z/OS UNIX system failure
File system type failure
Overview
JES2 processing
JES3 processing
Applications processing
Enabling the fastpath support for system authorization facility (SAF)
Determining problem causes
Messages
Diagnosing problems in application programs
Diagnosing hangs during z/OS UNIX initialization
Chapter 26. Managing a temporary file system (TFS)
Overview
Mounting the temporary file system
Unmounting a temporary file system
Using a temporary file system in a shared HFS environment
Chapter 27. Setting up for daemons
Overview
Establishing the correct level of security for daemons
UNIX level
BPX.DAEMON.FACILITY
Customizing the system for IBM-supplied daemons
Defining modules to program control
Steps for defining programs from load libraries to program control
Step for defining programs in HFS files to program control
Using sanction lists
Using sanction lists
Setting the shared library attribute
Handling dirty address spaces
Using enhanced program security
Customizing the system for IP-supplied daemons
Steps for customizing the system for IP-supplied daemons
Customizing the IBM-supplied daemons
Customizing the inetd daemon
Customizing the uucpd daemon
Customizing the rlogind daemon
Customizing the cron daemon
Starting and restarting daemons
Using & at the end of a command
Starting and restarting daemons
Steps for setting up security procedures for daemons
Giving daemon authority to vendor-written programs
Tracking down problems when setting up daemons and servers
Verifying the user OMVS segment
Step for verifying the user OMVS segment
Verifying the group OMVS segment
Step for verifying the group OMVS segment
Verifying that the sticky bit is on
Steps for verifying that the sticky bit is on
Using external links to access MVS load libraries
Step for using external links to access MVS load libraries
Finding modules that were not defined to program control
Steps for finding modules that were not defined to program control
Checking the daemon authority
Checking the server setup
Refreshing RACF in-storage data
Setting up for rlogin
Problem determination
Overview
Application services and security for DCE clients
Checking authority to use protected resources
Limitations of RACF client ACEE support
Documenting the security requirements
UNIX level: BPX.SERVER is not defined
z/OS UNIX level: BPX.SERVER is defined
RACF with enhanced program security, BPX.SERVER, and BPX.MAINCHECK
BPX.SERVER
Server setup
Overview
Using SMF Record Type 30
Preventing SMF Record Type 34 and 35 for SUBSYS OMVS
Using SMF Record Type 74
Using SMF Record Type 80
Using SMF Record Type 92
Monitoring process activity
Chapter 30. Tuning performance
Placing SCEERUN in the link pack area
Placing SCEERUN in the link list
Managing the run-time library with RTLS
Managing the run-time library in STEPLIBs
Improving compiler performance
Caching RACF user and group information in VLF
Moving HFS executables into the link pack area
Using the shared library extended attribute
Tuning limits in parmlib
Monitoring BPXPRMxx parameter limits
How they work
Recommendations
Example
Making sure that the sticky bit for the z/OS shell is on
Improving the z/OS shell performance
Setting environment variables
Activating medium-weight processes
The /tmp directory
Caching frequently-read files
OMVS command and TSO/E response time
Improving the performance of the make utility
Chapter 31. Setting up for sockets
Overview
Setting up for INET
Customizing BPXPRMxx for INET
Setting up for CINET
The internal routing table
Customizing BPXPRMxx for CINET
Specifying INADDRANYPORT and INADDRANYCOUNT
Requesting transport affinity
Host information
Service information
Protocol information
Resolver information
Overview
Assigning account numbers for forked address spaces
Modifying the accounting information for the OMVS and BPXOINIT address space
IEFUAV — user account validation exit
IEFUJI — job initiation exit
IEFUJV — job validation exit
IEFUSI — step initiation exit
Chapter 33. z/OS UNIX System Services Parallel Environment
Overview
Customizing X-Windows resources
Using host list file
Parallel Environment files
FOMTLINP module for login function
FOMTLOUT Module for logout Function
Appendix C. Accessibility
Using assistive technologies
Notices
SNA Network
SNA Network
TN3270-C TN3270-S rlogin-C rlogin-S telnet-C telnet-S
TN3270-C TN3270-S rlogin-C rlogin-S telnet-C telnet-S
-- TELNET 3270 Client -- TELNET 3270 Server -- rlogin Client -- rlogin Server -- telnet Client (not shown) -- telnet Server
-- TELNET 3270 Client -- TELNET 3270 Server -- rlogin Client -- rlogin Server -- telnet Client (not shown) -- telnet Server
TN3270-S
lpp
Active before
Attributes of directory jane as long as OMVS.JANE.HFS is mounted
inode of directory /
F FF
Figure
13.
Direct
mount
276
z/OS
V1R4.0
UNIX
System
Services
Planning
Using
direct
mount
The
root
file
system
should
be
set
up
so
that
it
does
not
require
frequent
changes
or
updates
(outside
of
SMP/E
maintenance).
To
achieve
this
we
will
allocate
an
intermediate
HFS
data
set
called
OMVS.USERS
and
mount
it
at
/u.
All
user
directories
that
are
added
will
reside
in
this
new
HFS
data
set
and
not
in
the
root
HFS
data
set.
Sample
JCL
to
allocate
this
intermediate
HFS
is
in
Figure
15.
Change
the
JCL
to
fit
your
environment.
The
next
thing
to
do
is
mount
this
new
intermediate
HFS
data
set
at
/u.
The
mount
can
be
performed
from
an
ID
that
has
superuser
authority
by:
v
Using
the
usr/sbin/mount
REXX
exec
from
the
shell
v
Using
the
TSO
MOUNT
command
v
Using
the
mount
shell
command
D
F FF
AUTOMOUNT FACILITY
FFF FF
user1, user2, userx..
(Automount Facility will dynamically allocate pseudo directories to act as mount points and mount HFS
data sets only when files are accessed)
Figure
14.
Automount
facility
//STEP01
EXEC
lpp
The
file
system
data
space,
SYSZBPX2,
is
useful
if
the
hang
condition
appears
to
be
due
to
a
file
system
latch.
For
more
information
on
the
DUMP
command,
particularly
on
specifying
a
large
number
of
operands,
see
z/OS
MVS
System
Commands.
Reviewing
dump
completion
information
After
the
dump
completes,
you
receive
an
IEA911E
message
indicating
whether
the
dump
was
complete
or
partial.
If
it
was
partial,
check
the
SDRSN
value.
If
insufficient
disk
space
is
the
reason,
delete
the
dump,
allocate
a
larger
dump
data
set,
and
request
the
dump
again.
Recovering
from
a
failure
The
operator
needs
to
recover
if
a
failure
occurs:
v
Kernel
failure:
As
a
result,
interactive
processing
in
the
shell
and
z/OS
UNIX
applications
fail.
v
File
system
type
failure:
z/OS
UNIX
continues
processing
even
though
the
file
system
type
is
not
operational.
Requests
to
use
the
files
in
any
file
systems
of
that
file
system
type
will
fail.
v
File
system
failure:
As
a
result,
some
files
cannot
be
used,
which
may
cause
programs
to
fail.
The
operator
starts
recovery
by
collecting
messages
and
a
dump,
if
written.
z/OS
UNIX
system
failure
If
the
z/OS
UNIX
system
fails,
the
operator
collects
problem
data,
which
includes
messages,
SVC
dumps,
and
SYS1.LOGREC
records
for
abends
and
decides
if
re-IPL
is
warranted.
The
work
in
progress
when
the
failure
occurred
is
lost
and
must
be
started
from
the
beginning.
File
system
type
failure
After
a
failure
of
a
file
system
type,
the
system
issues
message
BPXF014D.
In
response,
the
operator
or
automation
corrects
the
problem
as
indicated
by
previous
messages
and
then
enters
R
in
reply
to
message
BPXF014D.
File
system
failure
These
events
can
be
symptoms
of
file
system
failure:
v
0F4
abend
v
EMVSPFSFILE
return
code
v
EMVSPFSPERM
return
code
412
z/OS
V1R4.0
UNIX
System
Services
Planning
v
A
file
becomes
unrecognizable
or
unopenable
After
a
failure
of
a
file
system,
the
operator:
1.
Restores
the
HFS
data
set
with
the
data
set
from
the
previous
level.
For
more
information
on
recovering
an
HFS
data
set,
see:
v
z/OS
DFSMS
Migration
v
z/OS
DFSMShsm
Storage
Administration
Guide
2.
Asks
a
superuser
to
logically
mount
the
restored
HFS
data
set
with
a
TSO/E
MOUNT
command.
3.
Notifies
all
shell
users
that
when
they
invoke
the
shell
they
will
mount
a
back-level
file
system,
telling
them
the
mount
point.
(Use
the
wall
command
to
broadcast
a
message
to
all
shell
users.)
Files
added
since
the
back-level
data
set
was
saved
must
be
re-created
and
added
again.
If
the
physical
file
system
owning
the
root
fails,
or
if
the
root
file
system
is
unmounted,
the
operator
must
restore
the
root
file
system.
This
can
be
done
by
a
superuser
who
is
defined
with
a
home
directory
of
//SYSUT1
DD
/*
/*
/*
File System OMVS.ETC
TCPIP2TCPIP1 TCPIP3 TCPIP4CTC/ IUTSAMEH
Dissatisfied
Overall
How
satisfied
are
you
that
the
information
in
this
book
is:
Very
Dissatisfied
Easy
to
Easy
to
Well
Applicable
to
your
Please
tell
us
how
we
can
improve
this
book:
Thank
you
for
your
responses.
May
we
contact
you?
h
Yes
h
No
When
you
send
comments
to
IBM,
you
grant
IBM
a
nonexclusive
right
to
use
or
distribute
your
comments
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Name
Address
Company
or
Organization
Phone
No.
Readers’
Comments
Softcopy publications
IBM Systems Center publications
z/OS UNIX porting information
z/OS UNIX support
Workload Manager (WLM)
Time Sharing Options Extensions (TSO/E)
z/OS Communications Services (TCP/IP Services)
ISPF
Hardware considerations
Workstation connections
What you can do with z/OS UNIX System Services Application Services
Application programmers
Chapter 2. Migration overview
Developing a migration strategy
Actions required for all migrations
Installing books for the OHELP command
Creating separate HFS data sets for /etc, /dev, /tmp, and /var
Updating configuration files
Changing file attributes for certain utilities and the UUCP function
Command differences due to symbolic links
Updating security procedures
OS/390 V1R10 or z/OS UNIX V1R1 to z/OS UNIX V1R4
OS/390 UNIX V2R9 to z/OS UNIX V1R4
OS/390 UNIX V2R8 to z/OS UNIX V1R3
OS/390 UNIX V2R7 to z/OS UNIX V1R4
OS/390 UNIX V2R6 to z/OS UNIX V1R4
Chapter 4. z/OS UNIX Version 1 Release 4 overview
Release summary
Automove system list
Enhanced program security
Enhanced pthread support
Process start/end exits
zFS enhancements
Release summary
ISHELL enhancements
msys for Setup for z/OS UNIX
Shutting down z/OS UNIX without re-IPLing
Starting colony address space outside of JES
Unmounting file systems that leave the sysplex
Chapter 6. z/OS UNIX Version 1 Release 2 overview
Release summary
Preventing applications from being interrupted by signals
pread and pwrite enhancements
Release summary
Binary semaphore support
Large file support
Long long support
Monitoring BPXPRMxx values
pthread affinity service
Skulker shell script
Release summary
BPXPRMxx syntax checker
Shared library extended attribute
Release summary
Magic number
Release summary
inetd and rlogind daemons
UNIXMAP class
Release summary
BPXPRMxx
Overview
Establishing an /etc file system for a new release
Chapter 14. Customizing z/OS UNIX
Overview
Setting up kernel services
Evaluating virtual storage needs
Reducing the amount of ESQA needed to support servers
Prioritizing kernel work on your system
Running in goal mode
Defining classification rules as needed
Defining BPXPRMxx parmlib members in IEASYSxx
Customizing the BPXPRMxx parmlib members
Defining file systems
CTnBPXxx parmlib member to control tracing
IEADMR00 parmlib member to gather dump data
SMFPRMxx parmlib member to specify timeouts
Customizing the OMVS cataloged procedure to run the kernel initialization program
Running a physical file system in a colony address space
How to start colonies
Running a temporary file system in a colony address space
Enabling certain TSO/E commands to z/OS UNIX users
Setting up the REXX parameter modules
Checking for setup errors
Overview
What is a z/OS UNIX customization task?
Preparing to use msys for Setup
Using msys for Setup for z/OS UNIX customization
Chapter 16. Establishing UNIX security
Overview
Setting up users and groups
Activating supplemental groups
Security implications of programs running in the HFS
Authority checks
Obtaining security information for a group
Obtaining security information for a user
Setting up field-level access for the OMVS segment of a user profile
Defining group identifiers (GIDs)
Defining user identifiers (UIDs)
Setting user limits
Assigning UIDs and GIDs in an NFS network
Assigning identifiers for users and groups
Upper limits for GIDs and UIDs
Creating z/OS UNIX groups
Assigning superuser attributes
Using UNIXPRIV class profiles
Allowing z/OS UNIX users to change file ownerships
Using the CHOWN.UNRESTRICTED profile
Using the SUPERUSER.FILESYS.CHOWN profile
Steps for setting up BPX.SUPERUSER
Deleting superuser authority
Changing a superuser from UID(0) to a unique nonzero UID
Steps for changing a superuser from UID(0) to a unique nonzero UID
Switching in and out of superuser authority
Assigning a UID of 0
Setting up the BPX.* FACILITY class profiles
Security requirements for ServerPac and CBPDO installation
If you use uppercase group and user IDs
If you use mixed-case group and user IDs
If you have problems with names such as UUCP, UUCPG, and TTY
Defining cataloged procedures to RACF
Controlling access to files and directories
Setting classes for a user's process
Using the FILE.GROUPOWNER.SETGID profile
Changing the owner or group for a file
Creating a set-user-ID or set-group-ID executable file
Protecting data
Using access control lists (ACLs)
ACLs and ACL entries
How ACLs are used in file access checks
Auditing changes to ACLs
Auditing access to files and directories
Specifying file audit options
Steps for creating a sanction list
Steps for activating the sanction list
Maintaining the security level of the system
Steps for maintaining the security level of the system
Defining the OMVSAPPL profile for the APPL class
Setting up TCP/IP security
Overview
Using the Network File System (NFS)
Creating a hierarchical file system
Using uppercase and lowercase letters in filenames and pathnames
Allocating an HFS data set for the root file system
Defining the root file system
What happens when file systems are mounted?
Steps in mounting file systems
Restrictions on mounting file systems
Managing file systems
Removing unnecessary files from directories
Improving accesses to file systems
Unmounting file systems
Deciding how to mount your root HFS for execution
Leaving the root HFS mounted in read/write mode
Post-installation actions for mounting the root HFS in read-only mode
Mounting the root HFS in read-only mode
Customizing cron, uucp, and mail utilities for a read-only root HFS
Customizing the cron and uucp utilities
Customizing the mail utility
Copying the file system
Ways to back up HFS data sets
DFSMShsm
Using direct mount
Naming specific directories using the automount facility
Changing which data sets get automounted
Stopping the automount facility
System console file
Recovering from file system problems with the root
Installing service into the HFS
Example of installing service
Transporting the HFS from the driving system to the target system
Installing service into /etc
Chapter 18. Using the zSeries file system (zFS)
Overview
When would you want to use zFS?
zFS and shared sysplex
Overview
How the end user views the HFS
Summary of new HFS data sets
Comparing file systems in single system pre-OS/390 UNIX V2R9 and OS/390 UNIX V2R9 or later environments
File systems in single system pre-OS/390 UNIX V2R9 Environments
File systems in single system OS/390 UNIX V2R9 or later environments
File systems in OS/390 UNIX V2R9 or later sysplex environments
Procedures for establishing shared HFS in a sysplex
Steps in creating the sysplex root HFS data set
Steps in creating the system-specific HFS data sets
Steps in mounting the version HFS
Using the automove system list (SYSLIST)
Steps in creating an OMVS couple data set (CDS)
Steps in updating COUPLExx to define the OMVS CDS to XCF
Customizing BPXPRMxx for shared HFS
Sysplex scenarios showing shared HFS capability
Scenario 1: First system in the sysplex
Scenario 2: Multiple systems in the sysplex – using the same release level
Scenario 3: Multiple systems in a sysplex using different release levels
Keeping automount policies consistent on all systems in the sysplex
Steps in keeping your automount policy consistent on all systems
Moving file systems in a sysplex
Shared HFS implications during system failures and recovery
Shared HFS implications during a planned shutdown of z/OS UNIX
State of file systems after shutdown
File system initialization
Using distributed BRLM
Steps for setting up distributed BRLM on every system in the sysplex
Mounting file systems using NFS client mounts
File system availability
Read-write connections for sysplex-aware file systems
Read-only connections for non-sysplex aware file systems
Read-only connections for sysplex-aware file systems
Situations that can interrupt availability
Tuning z/OS UNIX performance in a sysplex
DFS considerations
Overview
By system programmer action
By TSO/E user action
Supplying an alternative shell
For the z/OS shell
For the tcsh Shell
Customizing files for the z/OS shell
Customizing /etc/profile
Customizing $HOME/.profile
Customizing /etc/init.options
Customizing /etc/rc
Customizing /etc/csh.login
Customizing /etc/csh.cshrc
Customizing /etc/complete.tcsh
Enabling utilities
Enabling the man pages
Customizing c89, cc, and c++ (cxx) compilers
Using the built-in c89/cc/c++ utility for the z/OS shell
Using non-default high-level qualifiers
Selecting C/C++ compilers
Setting up c89 to work with the current C/C++ compiler
Targeting an OS/390 release earlier than the current one
Targeting an earlier release
Customizing the terminfo database
Re-creating the terminfo database
For the z/OS shell
For the tcsh shell
Chapter 21. Customizing for your national code page in the shell
Overview
Steps for setting up your national code page
Customizing for Japanese and Simplified Chinese
Steps for customizing the login file for the z/OS shell
Steps for customizing the login file for the tcsh shell
Steps for displaying messages
TSO/E messages
PROFILE PLANGUAGE and the OMVS command
Chapter 22. Configuring the UNIX-to-UNIX copy program (UUCP)
Overview
Custom applications
Add an entry to the permissions file
Define the group ID and the user ID to RACF
If you use uppercase IDs
If you use mixed-case group and user IDs
If you have problems with using NUUPC
Configuring communication with remote systems
Obtain information about remote systems
Create or edit configuration files
Editing a configuration file
Compile the configuration files
Schedule periodic UUCP transfers with cron
Creating a crontab entry
Testing the connection
Contacting the remote site
Displaying information about recorded UUCP events
Notifying remote systems about password changes
Chapter 23. Using Enhanced ASCII functionality
Overview
Chapter 24. Managing operations
Terminating threads
Planned shutdowns using F BPXOINIT,SHUTDOWN=...
Steps for shutting down z/OS UNIX using F BPXOINIT,SHUTDOWN=...
Partial shutdowns (for JES2 maintenance)
Steps for partial shutdowns for JES2 maintenance
File system shutdown
What F OMVS,SHUTDOWN does
Dynamically changing the BPXPRMxx parameter values
Steps for dynamically changing certain BPXPRMxx parameter values
MAXPROCSYS
MAXPTYS
Activating the HFS file system for the first time
Activating a single sockets file system for the first time
Activating multiple sockets file systems for the first time with Common INET
Steps for increasing the MAXSOCKETS value
Adding another sockets file system to an existing Common INET configuration
Tracing events in z/OS UNIX
Steps for tracing events in z/OS UNIX
Steps for tracing DFSMS/MVS events
Steps for re-creating problems for IBM service
Displaying the status of the kernel
Steps for displaying the status of the kernel
Steps for displaying the status of BPXPRMxx parmlib limits
Taking a dump of the kernel and user processes
Steps for displaying the kernel address space
Steps for displaying process information
Steps for displaying global resource information
Steps for preallocating a sufficiently large dump data set
Steps for taking the dump
Reviewing dump completion information
Recovering from a failure
z/OS UNIX system failure
File system type failure
Overview
JES2 processing
JES3 processing
Applications processing
Enabling the fastpath support for system authorization facility (SAF)
Determining problem causes
Messages
Diagnosing problems in application programs
Diagnosing hangs during z/OS UNIX initialization
Chapter 26. Managing a temporary file system (TFS)
Overview
Mounting the temporary file system
Unmounting a temporary file system
Using a temporary file system in a shared HFS environment
Chapter 27. Setting up for daemons
Overview
Establishing the correct level of security for daemons
UNIX level
BPX.DAEMON.FACILITY
Customizing the system for IBM-supplied daemons
Defining modules to program control
Steps for defining programs from load libraries to program control
Step for defining programs in HFS files to program control
Using sanction lists
Using sanction lists
Setting the shared library attribute
Handling dirty address spaces
Using enhanced program security
Customizing the system for IP-supplied daemons
Steps for customizing the system for IP-supplied daemons
Customizing the IBM-supplied daemons
Customizing the inetd daemon
Customizing the uucpd daemon
Customizing the rlogind daemon
Customizing the cron daemon
Starting and restarting daemons
Using & at the end of a command
Starting and restarting daemons
Steps for setting up security procedures for daemons
Giving daemon authority to vendor-written programs
Tracking down problems when setting up daemons and servers
Verifying the user OMVS segment
Step for verifying the user OMVS segment
Verifying the group OMVS segment
Step for verifying the group OMVS segment
Verifying that the sticky bit is on
Steps for verifying that the sticky bit is on
Using external links to access MVS load libraries
Step for using external links to access MVS load libraries
Finding modules that were not defined to program control
Steps for finding modules that were not defined to program control
Checking the daemon authority
Checking the server setup
Refreshing RACF in-storage data
Setting up for rlogin
Problem determination
Overview
Application services and security for DCE clients
Checking authority to use protected resources
Limitations of RACF client ACEE support
Documenting the security requirements
UNIX level: BPX.SERVER is not defined
z/OS UNIX level: BPX.SERVER is defined
RACF with enhanced program security, BPX.SERVER, and BPX.MAINCHECK
BPX.SERVER
Server setup
Overview
Using SMF Record Type 30
Preventing SMF Record Type 34 and 35 for SUBSYS OMVS
Using SMF Record Type 74
Using SMF Record Type 80
Using SMF Record Type 92
Monitoring process activity
Chapter 30. Tuning performance
Placing SCEERUN in the link pack area
Placing SCEERUN in the link list
Managing the run-time library with RTLS
Managing the run-time library in STEPLIBs
Improving compiler performance
Caching RACF user and group information in VLF
Moving HFS executables into the link pack area
Using the shared library extended attribute
Tuning limits in parmlib
Monitoring BPXPRMxx parameter limits
How they work
Recommendations
Example
Making sure that the sticky bit for the z/OS shell is on
Improving the z/OS shell performance
Setting environment variables
Activating medium-weight processes
The /tmp directory
Caching frequently-read files
OMVS command and TSO/E response time
Improving the performance of the make utility
Chapter 31. Setting up for sockets
Overview
Setting up for INET
Customizing BPXPRMxx for INET
Setting up for CINET
The internal routing table
Customizing BPXPRMxx for CINET
Specifying INADDRANYPORT and INADDRANYCOUNT
Requesting transport affinity
Host information
Service information
Protocol information
Resolver information
Overview
Assigning account numbers for forked address spaces
Modifying the accounting information for the OMVS and BPXOINIT address space
IEFUAV — user account validation exit
IEFUJI — job initiation exit
IEFUJV — job validation exit
IEFUSI — step initiation exit
Chapter 33. z/OS UNIX System Services Parallel Environment
Overview
Customizing X-Windows resources
Using host list file
Parallel Environment files
FOMTLINP module for login function
FOMTLOUT Module for logout Function
Appendix C. Accessibility
Using assistive technologies
Notices