JES2 for Operators

LENGTH OF COURSE:
3 Days

DESCRIPTION: This course provides a comprehensive overview of JES2 Operations and Components. The course will concentrate on the operational requirements of a JES 2 environment. The instructor will review the concepts and issues associated with a job running an OS/390 environment. With easy-to-follow examples, the instructor will illustrate how OS/390 interacts with JES2 and review the daily operator task associated with JES2.

PREREQUISITES: Some Prior experiences and working knowledge of OS/390 systems.

INSTRUCTION TECHNIQUES: A combination of Lecture, Demonstration, and Hands-On Labs (when/where available)

AUDIENCE

JES2 operators, managers, support staff and system programmers.
KEY HIGHLIGHTS:

  • What is a JES?
    • How JES2 Fits into the OS/390 System
    • Relationship of JES2 to JCL and Submitted Jobs
    • JES2 Compared to JES3
    • Overview of JES2
  • How does JES2 manage its work?
  • Where does JES2 store its data, and how does JES2 provide integrity
  • What is spooling
  • What is checkpointing¦
  • What processing configurations does JES2 support
    • What is a multi-access spool complex
    • What is poly-JES
    • What is remote job entry
    • What is network job entry?
  • During the life of a job, what processing does JES2 do for OS/390
  • What are some of the major JES2 functions that make it special?
  • Review the Phases of Job Processing
  • Review the six phase of Job
    • Input Phase
    • Conversion Phase
    • Processing Phase
    • Output Phase
    • Hard-Copy Phase
    • Purge Phase
  • Explain the status of jobs:
    • Waiting to run - conversion queue
    • Currently running - execution queue
    • Waiting for their output to be produced - output queue
    • Having their output produced - hard-copy (print/punch) queue
    • Waiting to be purged from the system (following completion of all processing) - purge queue.


  • Tailoring Your JES2 System
  • How can JES2 be tailored at initialization to meet my installation's needs ?
  • Do I need to get so involved in customizing JES2 that I need to write 'operating system' code?
  • What other means can I use to enhance JES2 if it does not meet all my specific processing needs?
    • What are JES2 'table pairs'
    • What's the difference between an IBM-defined exit and an installation-defined exit?
  • Interacting with JES2
    • Communicating with JES2?
    • Operator control over JES2
    • Automating routine processing needs
    • JES2 problems
    • Diagnosis and recovery?
  • Stopping and Restarting & JES2 Commands
  • Operator commands can be used to:
    • Add function and functional subsystems
    • Modify previously defined processing, such as: output definition, the dynamic alteration of the checkpoint definition, enabling installation-defined exits, offload devices, printer and punch characteristics, and job characteristics
    • Delete function, and network systems, exits, and diagnostic traces
    • Start, stop, and halt devices under JES2's control
    • Assign units to local printers, punches, card readers, and lines or reassign units to these devices


  • Display current facility and device definition.
    • JES2 Messages
    • JES2 Tracing Facility
    • JES2-IPCS Formatting
  • OS/390 JES2 Diagnosis
  • Diagnostic aids/tools and their output
  • Identify a problem
  • Collect information about the problem
  • Report the problem

Return to Home Page.
Return to Alphabetic Listing of Courses.
Return to Courses by Subject.
Request More Information or Contact Us.