Re: SMS ACS ROUTINE VARIABLES
In 1435930441.72432.yahoomailba...@web125906.mail.ne1.yahoo.com, on 07/03/2015 at 06:34 AM, willie bunter 001409bd2345-dmarc-requ...@listserv.ua.edu said: would a @* work because the job(s) are submitted by the scheduler? It doesn't matter who submitted it, only the userid it is running under. USER=* will match USER=FOO even if it is not submittd by the scheduler. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
The client wants it that way. No other explanation given by the client. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
My recommendation is to try it. It is the best teaching tool. And remember to ISMF TEST function for testing ACS code Remember to follow the conventions needed to code masked variables vs. specific data for variables. So long as the name follows normal z/OS policy - you should be fine. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, July 03, 2015 6:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMS ACS ROUTINE VARIABLES I saw the USER variable in the doc but I was thrown off track when I read the explanation of USER which says the following : The user ID of the person allocating the dataset. I would like to try your suggestion however since we have multiple batch users begining @ would a @* work because the job(s) are submitted by the scheduler? On Thu, 7/2/15, Greg Shirey wgshi...@benekeith.com wrote: Subject: Re: SMS ACS ROUTINE VARIABLES To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, July 2, 2015, 1:46 PM USER is the User ID associated with the batch job. If you have a FILTLIST of the User IDs called, say, NOPDSES, then you can code: WHEN (USER EQ NOPDSES AND DSNTYPE EQ 'LIB') THEN DO WRITE 'NOT ALLOWED FOR PDSE' EXIT CODE(12) END HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
I saw the USER variable in the doc but I was thrown off track when I read the explanation of USER which says the following : The user ID of the person allocating the dataset. I would like to try your suggestion however since we have multiple batch users begining @ would a @* work because the job(s) are submitted by the scheduler? On Thu, 7/2/15, Greg Shirey wgshi...@benekeith.com wrote: Subject: Re: SMS ACS ROUTINE VARIABLES To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, July 2, 2015, 1:46 PM USER is the User ID associated with the batch job. If you have a FILTLIST of the User IDs called, say, NOPDSES, then you can code: WHEN (USER EQ NOPDSES AND DSNTYPE EQ 'LIB') THEN DO WRITE 'NOT ALLOWED FOR PDSE' EXIT CODE(12) END HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
A point of curiosity. Why are your users not allowed to create PDSE datasets? - -teD - Original Message From: willie bunter Sent: Friday, July 3, 2015 09:34 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: SMS ACS ROUTINE VARIABLES I saw the USER variable in the doc but I was thrown off track when I read the explanation of USER which says the following : The user ID of the person allocating the dataset. I would like to try your suggestion however since we have multiple batch users begining @ would a @* work because the job(s) are submitted by the scheduler? On Thu, 7/2/15, Greg Shirey wgshi...@benekeith.com wrote: Subject: Re: SMS ACS ROUTINE VARIABLES To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, July 2, 2015, 1:46 PM USER is the User ID associated with the batch job. If you have a FILTLIST of the User IDs called, say, NOPDSES, then you can code: WHEN (USER EQ NOPDSES AND DSNTYPE EQ 'LIB') THEN DO WRITE 'NOT ALLOWED FOR PDSE' EXIT CODE(12) END HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
Or, if you want to prevent ALL users from creating PDS/E datasets, then you can make a more general ACS statement. There are some functions that need to create PDS/E datasets. So figure out which is the easier to maintain A FILTLIST with an INCLUDE for 1) Users that can create PDS/E Or 2) Users that cannot create PDS/E Remember, if you are planning to go to Enterprise COBOL V5 and above, datasets for the Cobol Compiler and the Load Module will need to be PDS/E datasets. Based on what I have seen for PDS/E V2 - I can see at some point that IBM might make a direction statement that PDS datasets should only be PDS/E datasets. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tabor, Rich Sent: Friday, July 03, 2015 7:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMS ACS ROUTINE VARIABLES Comparing USER to JOB might be useful. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, July 03, 2015 6:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] SMS ACS ROUTINE VARIABLES I saw the USER variable in the doc but I was thrown off track when I read the explanation of USER which says the following : The user ID of the person allocating the dataset. I would like to try your suggestion however since we have multiple batch users begining @ would a @* work because the job(s) are submitted by the scheduler? On Thu, 7/2/15, Greg Shirey wgshi...@benekeith.com wrote: Subject: Re: SMS ACS ROUTINE VARIABLES To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, July 2, 2015, 1:46 PM USER is the User ID associated with the batch job. If you have a FILTLIST of the User IDs called, say, NOPDSES, then you can code: WHEN (USER EQ NOPDSES AND DSNTYPE EQ 'LIB') THEN DO WRITE 'NOT ALLOWED FOR PDSE' EXIT CODE(12) END HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? How does USER not satisfy your needs? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SMS ACS ROUTINE VARIABLES
Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMS ACS ROUTINE VARIABLES
USER is the User ID associated with the batch job. If you have a FILTLIST of the User IDs called, say, NOPDSES, then you can code: WHEN (USER EQ NOPDSES AND DSNTYPE EQ 'LIB') THEN DO WRITE 'NOT ALLOWED FOR PDSE' EXIT CODE(12) END HTH, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Thursday, July 02, 2015 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMS ACS ROUTINE VARIABLES Hallo All, I am stuck with trying to figure out how I can code the variable for a Batch userid. For examle users aren't allowed to create a PDSe. I thought by coding the condition for the user's batch id it would solve the problem. However, I looked at all the SMS ACS read variable list but there is none for a batch id. Could anyone suggest how I can go about this? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
