IBM OS/390 User Manual
2.3.1.2 Automation
VSE customers who use OCCF and/or ISV products to provide console
automation functions will find enhanced function in the OS/390 environment.
Because of the availability of functions such as DFSMSrmm and DFSMShsm
consideration will have to be given to how to best implement these functions,
starting with the development of storage and media policies. ISV products also
exist in the OS/390 environment to provide additional automation capabilities.
automation functions will find enhanced function in the OS/390 environment.
Because of the availability of functions such as DFSMSrmm and DFSMShsm
consideration will have to be given to how to best implement these functions,
starting with the development of storage and media policies. ISV products also
exist in the OS/390 environment to provide additional automation capabilities.
2.3.1.3 Console Operator Interface
VSE console operators tend to have a significant amount of interaction with the
system console. This can be referred as a
system console. This can be referred as a
′
chatty
′
interface. Many batch
applications depend upon operator responses to function correctly. For example,
an operator may be required to enter date information and response verification
in order for a program to continue. Such facilities are not provided in OS/390
requiring these type of applications to be redesigned.
an operator may be required to enter date information and response verification
in order for a program to continue. Such facilities are not provided in OS/390
requiring these type of applications to be redesigned.
OS/390 provides the Message Processing Facility (MPF) which controls console
message processing and message display. MPF is similar in function to VSE
OCCF.
message processing and message display. MPF is similar in function to VSE
OCCF.
2.3.1.4 JCL Processing
VSE JCL syntax and structure is very forgiving and flexible. Users often exploit
this capability to enhance user productivity. For example, users often
intentionally code invalid JCL statements so that they may appear on the system
console for the correct information to be entered. This, then, provides a
somewhat crude way of creating dynamic JCL decks. This capability exists
because of the manner in which VSE POWER performs JCL processing. POWER
does JCL syntax checking at job execution time. When an invalid statement is
encountered the console operator is given the opportunity to enter the correct
statement. OS/390, however, does not provide such a capability because of the
way JES is designed. With JES, JCL syntax checking is performed at job
submission time. Jobs with invalid statements are rejected at this point and,
therefore, not executed. Consideration will need to be given to POWER
jobstreams that are designed in such a manner.
this capability to enhance user productivity. For example, users often
intentionally code invalid JCL statements so that they may appear on the system
console for the correct information to be entered. This, then, provides a
somewhat crude way of creating dynamic JCL decks. This capability exists
because of the manner in which VSE POWER performs JCL processing. POWER
does JCL syntax checking at job execution time. When an invalid statement is
encountered the console operator is given the opportunity to enter the correct
statement. OS/390, however, does not provide such a capability because of the
way JES is designed. With JES, JCL syntax checking is performed at job
submission time. Jobs with invalid statements are rejected at this point and,
therefore, not executed. Consideration will need to be given to POWER
jobstreams that are designed in such a manner.
2.3.1.5 Management Disciplines
Because of OS/390
′
s enhanced systems management capabilities, thought needs
to be given to system management, and its various disciplines, and how it will
be implemented in the OS/390 environment. OS/390 provides functions and
capabilities in each of the systems management areas. Specifically these are:
be implemented in the OS/390 environment. OS/390 provides functions and
capabilities in each of the systems management areas. Specifically these are:
•
Change control
•
Problem control
•
Performance management
•
Capacity planning
•
Configuration management
Chapter 2. Sizing the Effort
25