Filter
Top Products
Other MVS Names
There are many other objects which require naming in OS/390. Here is just a
sample:
•
Users (TSO, online, batch, operators)
•
Job names
•
Job step names
•
JCL procedure names and proclibs
•
Application program names
•
WLM service classes
•
WLM resource environments
25.4.1.3 JCL Standards
You should set up JCL (job control language) standards for your batch jobs, as
well as started tasks and TSO logon procedures. Here is a partial list of some of
the attributes to include in your JCL rules:
•
Job Attributes
Job names
Accounting information
Job classes
MSGCLASS and MSGLEVEL
Specification of USER, GROUP, SECLABEL, and PASSWORD
Use of JOBCATs, JOBLIBs
Estimated lines, bytes, pages, and cards
Use of PRTY, PERFORM, REGION, TIME parameters
Job restart options
Use of commands in the jobstream
•
Step Attributes
Job step names
Use of ACCT, DPRTY, PERFORM, REGION, TIME parameters
Use of STEPLIBs and STEPCATs
•
Data Set Attributes
Unit names
GDGs
Tape standard labels
DASD space units and parameters
Output classes and printer attributes
Output routing destinations
25.4.2 Systems Management Procedures
In general, you can use many of the same processes that you are currently
using. There are tools and products specific to OS/390 such as SystemView, TME
10, and INFO/MAN. Many products that work with VSE also work on OS/390.
This section addresses some of the basic elements associated with good
management practices of running a system. See Chapter 30, “Systems
Management Philosophy and Methodology” on page 457 for a more complete
discussion.
Chapter 25. Prepare the Migration Environment 409