Which statements concerning the JCLLIB statement are true?
-
There is either a JCLLIB statement for the entire JOB, or a separate one for each EXEC
-
A JCLLIB statement can not have a statement name.
-
There can only be one JCLLIB statement per JOB.
-
A JCLLIB statement must be coded before the first EXEC statement.
JCLLIB statement rules in JCL are specific. Option C is correct because only one JCLLIB statement is allowed per JOB - it defines the private library for the entire job. Option D is correct because JCLLIB must be placed before the first EXEC statement in the job. Option A is incorrect because JCLLIB is job-scoped, not per EXEC. Option B is incorrect because JCLLIB is a statement type itself and follows JCL naming rules. The JCLLIB statement enables cataloged procedure access by specifying a private library search order.
In JCL, only one JCLLIB statement is permitted per job — it applies to the whole job, not per-step — and it must physically appear before the first EXEC statement so that the job libraries it names are available when steps are located and executed.