"An attempt was made to run JES2 as other than a subsystem started task (for example, as a batch job).". There seems to be a discrepancy between the two manuals as to whether it is legal. Are you using documentation at the same level as your system? IAC, HASJESCK should work, as should running JES2 as a secondary subsystem.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Charles Mills [[email protected]] Sent: Friday, April 17, 2020 2:40 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? Hmmm. I decided to try DSCHECK *before* I made any changes. (I have gotten conservative in my old age.) I copied the JES2 PROC into a job. The EXEC statement now says //IEFPROC EXEC PGM=HASJES20,PARM=(CHECK), // DPRTY=(15,15),TIME=1440,PERFORM=9 I changed HASPLIST to SYSOUT=* I am getting $HASP433 INVALID SUBSYSTEM EXECUTION MODE and an RC=20 which makes sense -- but there is no output to HASPLIST. Thoughts? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Jacobs Sent: Friday, April 17, 2020 11:20 AM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? Here are some ideas. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.hasa300/run_dscheck.htm Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://secure-web.cisco.com/1bRUUjpRM8BIby-cka8iSYwy0KaPSHKyfv8uSs1DqyHcHaOuA-3c6Z5VXCM3r1PgKAEGOCFnpc7P0jZM3F_0IRuk867w2kfvO0b2eFLJv0N6ifejf1TC_YlZHZdJDPrt3bhS0NXwp_eabuGaZZNZytgmoAtfVbxaIhfaZzGFX73cD6WRhSyNIIHYibQbGRqTHBexeCDkCrd2ARJCkszAGq1Y8tQYUooaQ2VibdPbKKzC25ZCfuf54NT_KkD1x66t7oQmBMc8V0eI646LDJ_A5SH0roWSsFq9IAKmE4sTV9W9TJh9E6yoiD1EL7djMWKNS93Es-DFAml2MGR7qJMhNRwOY7QSu12hSudEtlkEw4muX5z8IKf-6rWNDfcwSVw0JGrM3DHA9r_MPedPD1E7EcG8yb7zFro2w10uK65FmynICb7Uv8w0FLRtq7Lcx879N/https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, April 17, 2020 1:44 PM, Charles Mills <[email protected]> wrote: > Humor me. I'm an experienced developer playing newbie sysprog in my spare > time. > > I've got a JES2 system where I want to change the order of job classes for > some of the initiators. I could get professional help but it is a service > bureau so that involves opening a ticket, dollars, etc., etc. > > I have done it through SDSF and all is well. I now want to make the change > persistent. I have JES2PARM open in an editor. I can make the changes very > carefully. > > Questions: (1) is there any way to test it, particularly that I have not > fouled it up terribly? The next IPL is probably months away, and a failure > would be very unpleasant. Is there any sort of non-disruptive "TYPRUN=SCAN" > sort of option to get JES2 to say the parm file is or is not okay? > > (2) alternatively, what would happen if it were bad? Suppose I fat-fingered > a comma? Unusable system? I am not sure what I am looking at but it looks to > me like TCPIP and TCAS are running under JES2. > > Thanks much, > > Charles > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
