On Fri, Jul 22, 2016 at 2:36 PM, Jesse 1 Robinson <jesse1.robin...@sce.com>
wrote:

> I think Peter is on the right track. I normally do not code any CLASS= on
> a job. Execution class here gets set by some pretty involved code in Exit
> 6, but the question is what 'jobclass' is used for options during
> conversion?
>
> If I omit CLASS=, my job works, implying that 'class A' rules are in
> effect. Changing nothing else, I added CLASS=C (unmodified) to the job
> card, and I get the same 'invalid use of ampersand' error that I started
> with. Then I set JOBCLASS(C) to allow SYSSYM, and the job worked.
>
> So again, what determines conversion rules if no CLASS= is coded? I cannot
> find any parameter in our JES2 init deck that would set class A as the
> default.
>

​Not necessarily definitive, due to language
ref:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/iea3b6_Defaults47.htm

<quote>

If you do not specify the CLASS keyword, JES uses the installation default
specified at initialization, as follows:

   - In a JES2 system, the default is based on the source of the job: The
   system makes the job’s class the same as the installation-specified default
   class for the particular card reader, work station, or time-sharing user
   that submitted the job.
   - In a JES3 system, the default is an installation-defined standard
   default class.


</quote>
​
​Looking at the above, I would guess that you are submitting this from TSO.
So it would be the default in your TSO segment in RACF.
ref:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.icha700/tsosup.htm
Does not answer the question if the JOBCLASS entry in the TSO segment is
not entered.
futher information:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa400/has2u600110.htm
<quote>

DEF_CLASS=class|A[image: End of change][image: Start of change]Specifies a
default class that JES2 will use if a non-valid class is discovered during
processing. The specified class must be a defined and active batch job
class. The specified class cannot be set to ACTIVE=NO, and cannot be
deleted. The following examples show when the default class would be used:

   - When a job is submitted with a CLASS= value that is not valid. The job
   is failed, but this class is associated with the job for later processing.
   - When a job class is deleted that is associated with the INTRDR
   statement as CLASS=. The INTRDR CLASS value is set to this value.
   - During initialization processing, when the CLASS= value that is
   specified for a reader (INTRDR, local or remote) is not valid and the
   operator continues initialization.

The default is A.

</quote>
​




>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
>
-- 
"Worry was nothing more than paying interest on a loan that a man may never
borrow"

From: "Quest for the White Wind" by Alan Black

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to