Planning for security

You and your JES system programmer should develop a security plan for JES. Together, you should determine which resources you want to protect and decide who should have access to those resources. Your security plan should address questions such as:

What resources must I protect?
Should I restrict jobs and users from certain information depending on criteria such as security labels?
Should I limit the job names that users can submit, cancel, or modify?
Is it important to protect SYSIN and SYSOUT?
Which remote workstations should access my system?
Can other nodes submit jobs to my system?
To which nodes should I allow my system to send data?
Should I limit the commands that an operator can use?
Do I want to restrict the consoles that an operator can use to enter certain commands?
What commands should I allow jobs, workstations, and nodes to submit to my system?
Do I want only selected output devices to process particular output?
Should the security label of the output appear on the header pages?

You must gather a great deal of information from your JES system programmer about specific resources and access requirements. If JES2 is installed on your system, the JES system programmer should use z/OS JES2 Initialization and Tuning Guide.

If JES3 is installed on your system, the JES system programmer should use z/OS JES3 Initialization and Tuning Guide.