Re: ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
ABEND S0C4 was overloaded since SVS, but I remember seeing the correct 
interrupt code reported on dumps and in APAR descriptions, e.g., PK00040.

What I really want is a separate ABEND code and SPIE mask bit for each type of 
program check, but that ship has sailed.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jim 
Mulder [d10j...@us.ibm.com]
Sent: Sunday, March 6, 2022 10:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

  It has worked that way for PIC x'10' and x'11' since MVS/XA,  40 years ago.
'38' - x'3B' were added via APAR OW57082, 19 years ago.

  It looks to me like the original interrupt code would be in STCBOLCP,
but STCBOLCP is not designated as a Programming Interface.
What you would really want is for the original interrupt code to
be provided in one of the IHAEPIE fields that is currently reserved.
Unfortunately, OW57082 did not do that.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 5:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Ouch! Those overloaded odes make diagnosis more difficult.

Thanks.


--
Shmuel (Seymour J.) Metz
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7C6f047fafd55d4a1c58a308d9ffec8583%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637822213620474251%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=P%2FoT2daoya372VBjIOQpCOvgmMsno%2BHd%2FwxPXvHkoS4%3Dreserved=0


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jim 
Mulder [d10j...@us.ibm.com]
Sent: Sunday, March 6, 2022 3:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

  The code did not work, and appeared to have not worked for a
long time.   We could not come up with any use for a function
that would give control to an ESPIE exit before invoking the Real Storage 
Manager for a DAT exception.  There would not seem to be anything useful that 
an ESPIE exit could do in that case, since it would not know whether or not the 
Real Storage Manager would be able to resolve the exception.

 The ISVs were notified, and I don't remember any objections.

  Note that for Program Interrupt Codes  x'10', x'11',x'38, x'39,' x'3A', and 
x'3B', an exception that does not get resolved by the Real Storage Manager will 
get presented to SPIE/ESPIE exits as interrupt code 4.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 10:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Thanks. Any idea why they took it away?


--
Shmuel (Seymour J.) Metz
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7C6f047fafd55d4a1c58a308d9ffec8583%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637822213620474251%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=P%2FoT2daoya372VBjIOQpCOvgmMsno%2BHd%2FwxPXvHkoS4%3Dreserved=0


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1-15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
ssage: 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: ESPIE IC > 15?

2022-03-06 Thread Jim Mulder 
  It has worked that way for PIC x'10' and x'11' since MVS/XA,  40 years ago.
'38' - x'3B' were added via APAR OW57082, 19 years ago.

  It looks to me like the original interrupt code would be in STCBOLCP,
but STCBOLCP is not designated as a Programming Interface. 
What you would really want is for the original interrupt code to 
be provided in one of the IHAEPIE fields that is currently reserved. 
Unfortunately, OW57082 did not do that. 

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 5:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Ouch! Those overloaded odes make diagnosis more difficult.

Thanks.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jim 
Mulder [d10j...@us.ibm.com]
Sent: Sunday, March 6, 2022 3:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

  The code did not work, and appeared to have not worked for a
long time.   We could not come up with any use for a function
that would give control to an ESPIE exit before invoking the Real Storage 
Manager for a DAT exception.  There would not seem to be anything useful that 
an ESPIE exit could do in that case, since it would not know whether or not the 
Real Storage Manager would be able to resolve the exception.

 The ISVs were notified, and I don't remember any objections.

  Note that for Program Interrupt Codes  x'10', x'11',x'38, x'39,' x'3A', and 
x'3B', an exception that does not get resolved by the Real Storage Manager will 
get presented to SPIE/ESPIE exits as interrupt code 4.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 10:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Thanks. Any idea why they took it away?


--
Shmuel (Seymour J.) Metz
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Caea322dbb0c44b5137a408d9ffafa33b%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821952103800693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=FMCl5U%2FkJlSZ36YrRoq%2FmvGmLX6fPn%2BrvocyLWTeV4c%3Dreserved=0


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1-15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
ssage: 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: ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
Ouch! Those overloaded odes make diagnosis more difficult.

Thanks.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jim 
Mulder [d10j...@us.ibm.com]
Sent: Sunday, March 6, 2022 3:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

  The code did not work, and appeared to have not worked for a
long time.   We could not come up with any use for a function
that would give control to an ESPIE exit before invoking the Real Storage 
Manager
for a DAT exception.  There would not seem to be anything useful that an
ESPIE exit could do in that case, since it would not know whether or
not the Real Storage Manager would be able to resolve the exception.

 The ISVs were notified, and I don't remember any objections.

  Note that for Program Interrupt Codes  x'10', x'11',x'38, x'39,' x'3A',
and x'3B', an exception that does not get resolved by the Real Storage Manager
will get presented to SPIE/ESPIE exits as interrupt code 4.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 10:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Thanks. Any idea why they took it away?


--
Shmuel (Seymour J.) Metz
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Caea322dbb0c44b5137a408d9ffafa33b%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821952103800693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=FMCl5U%2FkJlSZ36YrRoq%2FmvGmLX6fPn%2BrvocyLWTeV4c%3Dreserved=0


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1–15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
ssage: 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: Job submission from CMS to MVS

2022-03-06 Thread Tony Thigpen 

Shmuel,

I use have the VM 'submit' exec spool it to a disconnected user that in 
turn submits the jcl to z/OS via FTP. I use RSCS to get the output back 
to the original user (if needed).


I use FTP because I don't have RACF on z/VM and RSCS does not properly 
pass the credentials without having RACF on z/VM. (At least that is the 
information I had when I set this up several years ago.) I originally 
wanted to update the RSCS exits, which I have done in the past, but I 
never got back to it.


In my case, z/OS runs on a completely separate CPU. I have actually 
played with running z/OS under z/VM and unless you have a 
multi-processor, it kills performance. I also run z/VSE under z/VM and 
they play really well together.


Tony Thigpen

Seymour J Metz wrote on 3/6/22 09:58:

There are two obvious way to submit an MVS job from CMS:

  1. Spool it ti RSCS and let it go in via NJE

  2. Spool it to a virtual reader on MVS

I'm curious as to how many shops do which, and how they're configured.



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

--
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: ESPIE IC > 15?

2022-03-06 Thread Jim Mulder 
  The code did not work, and appeared to have not worked for a 
long time.   We could not come up with any use for a function 
that would give control to an ESPIE exit before invoking the Real Storage 
Manager
for a DAT exception.  There would not seem to be anything useful that an 
ESPIE exit could do in that case, since it would not know whether or
not the Real Storage Manager would be able to resolve the exception.

 The ISVs were notified, and I don't remember any objections.

  Note that for Program Interrupt Codes  x'10', x'11',x'38, x'39,' x'3A', 
and x'3B', an exception that does not get resolved by the Real Storage Manager
will get presented to SPIE/ESPIE exits as interrupt code 4. 

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. Poughkeepsie NY

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Sunday, March 6, 2022 10:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Thanks. Any idea why they took it away?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1–15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only 
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
ssage: 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: ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
Even if MVS marked unused segment table entries as invalid, processing PGM 
IC=16 ('10'X) would be much faster because allocating an empty page table 
wouldn't require any I/O.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Steve Smith [sasd...@gmail.com]
Sent: Sunday, March 6, 2022 1:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Well, why was 17 allowed, but not 16?  That seems random, and at least it's
consistent now.  Along with the codes for region table exceptions.

And anyway, supervisor state is not allowed, much less required.

sas

On Sun, Mar 6, 2022 at 11:06 AM Seymour J Metz  wrote:

> The use of ESPIE with IC 17 was documented in the authorized macro
> reference, so it was available for customer use. It's no more restricted
> than, e.g., ATTACH RSAPF=YES, and doesn't even reqquire Supervisor mode,
> just APF or system key. I'm hoping someone from IBM knows.
>
>

--
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: ESPIE IC > 15?

2022-03-06 Thread Steve Smith 
Well, why was 17 allowed, but not 16?  That seems random, and at least it's
consistent now.  Along with the codes for region table exceptions.

And anyway, supervisor state is not allowed, much less required.

sas

On Sun, Mar 6, 2022 at 11:06 AM Seymour J Metz  wrote:

> The use of ESPIE with IC 17 was documented in the authorized macro
> reference, so it was available for customer use. It's no more restricted
> than, e.g., ATTACH RSAPF=YES, and doesn't even reqquire Supervisor mode,
> just APF or system key. I'm hoping someone from IBM knows.
>
>

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

Re: Job submission from CMS to MVS

2022-03-06 Thread Dave Jones 
Shmuel I use RSCS to z/OS 2.4 here; works great.
DJ

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

Re: Job submission from CMS to MVS

2022-03-06 Thread Seymour J Metz 
I was thinking of CMS and MVS under the same CP. Yes, I forgot that FTP was 
another option, and I'd like to see those numbers as well.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Sunday, March 6, 2022 10:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Job submission from CMS to MVS

On Mar 6, 2022, at 07:58:17, Seymour J Metz wrote:
>
> There are two obvious way to submit an MVS job from CMS:
>
> 1. Spool it ti RSCS and let it go in via NJE
>
> 2. Spool it to a virtual reader on MVS
>
 (Not for real MVS.)

 3. (Not obvious?)  FTP SITE FILE=JES.
(Works alike from desktops.)

> I'm curious as to how many shops do which, and how they're configured.

--
gil

--
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: Job submission from CMS to MVS

2022-03-06 Thread Seymour J Metz 
Is there a workstation program for  CMS? That would certainly work, and I'd be 
curious how many are using it, or SNA from CMS, for that matter.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
David Spiegel [dspiegel...@hotmail.com]
Sent: Sunday, March 6, 2022 10:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Job submission from CMS to MVS

Hi R'Shmuel AMV"SH,
Gut Voch

How about via TCP/IP from CMS?

Regards,
David

On 2022-03-06 09:58, Seymour J Metz wrote:
> There are two obvious way to submit an MVS job from CMS:
>
>   1. Spool it ti RSCS and let it go in via NJE
>
>   2. Spool it to a virtual reader on MVS
>
> I'm curious as to how many shops do which, and how they're configured.
>
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Cede3d9b8ddf54f69c05908d9ff88108d%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821782150842402%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=kuwQUI5jc1lV92iDzwHt0l9zdXehkO0fwKGdqYDxZOA%3Dreserved=0
>
> --
> 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: ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
The use of ESPIE with IC 17 was documented in the authorized macro reference, 
so it was available for customer use. It's no more restricted than, e.g., 
ATTACH RSAPF=YES, and doesn't even reqquire Supervisor mode, just APF or system 
key. I'm hoping someone from IBM knows.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

"The following description of the SPIE macro also appears in z/OS MVS
Programming: Assembler Services Reference ABE-HSP
,
with the exception of interruption type 17. This interruption type
designates page faults and its use is restricted to an authorized program."

Probably because it was restricted use.

Joe

On Sun, Mar 6, 2022 at 9:18 AM Seymour J Metz  wrote:

> Thanks. Any idea why they took it away?
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Cc33fd6120ec248f1401208d9ff890339%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821786219623156%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=yd9qOpPMyGjMu%2FlamHkJNcp7H%2FmWhi1PEG%2Fbjet8uQQ%3Dreserved=0
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Joe Monk [joemon...@gmail.com]
> Sent: Sunday, March 6, 2022 10:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ESPIE IC > 15?
>
> Looks like as of z/OS 2.3.
>
> 2.2 doc:
>
> If a program interruption occurs, the SPIE/ESPIE exit receives control only
> when all of the following conditions exist:
>
>- The interrupted program is a problem state program.
>- The program interrupt code is in the range 1–15 and 17.
>
> 2.3 doc:
>
> If a program interruption occurs, the SPIE/ESPIE exit receives control only
> when all of the following conditions exist:
>
>- The interrupted program is a problem state program.
>- The program interrupt code is in the range 1 - 15.
>
> Joe
>
> On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:
>
> > When did ESPIE stop supporting interrupt code 17?
> >
> > --
> > Shmuel (Seymour J.) Metz
> >
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Cc33fd6120ec248f1401208d9ff890339%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821786219623156%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=yd9qOpPMyGjMu%2FlamHkJNcp7H%2FmWhi1PEG%2Fbjet8uQQ%3Dreserved=0
> >
> > --
> > 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
>

--
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: ESPIE IC > 15?

2022-03-06 Thread Joe Monk 
"The following description of the SPIE macro also appears in z/OS MVS
Programming: Assembler Services Reference ABE-HSP
,
with the exception of interruption type 17. This interruption type
designates page faults and its use is restricted to an authorized program."

Probably because it was restricted use.

Joe

On Sun, Mar 6, 2022 at 9:18 AM Seymour J Metz  wrote:

> Thanks. Any idea why they took it away?
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Joe Monk [joemon...@gmail.com]
> Sent: Sunday, March 6, 2022 10:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ESPIE IC > 15?
>
> Looks like as of z/OS 2.3.
>
> 2.2 doc:
>
> If a program interruption occurs, the SPIE/ESPIE exit receives control only
> when all of the following conditions exist:
>
>- The interrupted program is a problem state program.
>- The program interrupt code is in the range 1–15 and 17.
>
> 2.3 doc:
>
> If a program interruption occurs, the SPIE/ESPIE exit receives control only
> when all of the following conditions exist:
>
>- The interrupted program is a problem state program.
>- The program interrupt code is in the range 1 - 15.
>
> Joe
>
> On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:
>
> > When did ESPIE stop supporting interrupt code 17?
> >
> > --
> > Shmuel (Seymour J.) Metz
> >
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Ce7d33597cb63465d355808d9ff8466c4%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821766401766103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=87%2BUdZukaha2fWu49Kw7EdyflfFJJTluGpn6D7xKIQc%3Dreserved=0
> >
> > --
> > 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
>

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

Re: Job submission from CMS to MVS

2022-03-06 Thread David Spiegel 

Hi R'Shmuel AMV"SH,
Gut Voch

How about via TCP/IP from CMS?

Regards,
David

On 2022-03-06 09:58, Seymour J Metz wrote:

There are two obvious way to submit an MVS job from CMS:

  1. Spool it ti RSCS and let it go in via NJE

  2. Spool it to a virtual reader on MVS

I'm curious as to how many shops do which, and how they're configured.



--
Shmuel (Seymour J.) Metz
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7C%7C9db02af512ce4818f21d08d9ff81ce80%7C84df9e7fe9f640afb435%7C1%7C0%7C637821755318108310%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=zgeXE79l%2FznSzFUh%2BP0v4sNKJx0OB3h2NGvty95sPQ8%3Dreserved=0

--
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: Job submission from CMS to MVS

2022-03-06 Thread Paul Gilmartin 
On Mar 6, 2022, at 07:58:17, Seymour J Metz wrote:
> 
> There are two obvious way to submit an MVS job from CMS:
> 
> 1. Spool it ti RSCS and let it go in via NJE
> 
> 2. Spool it to a virtual reader on MVS
>  
 (Not for real MVS.)

 3. (Not obvious?)  FTP SITE FILE=JES.
(Works alike from desktops.)

> I'm curious as to how many shops do which, and how they're configured.

-- 
gil

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

Re: ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
Thanks. Any idea why they took it away?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joe 
Monk [joemon...@gmail.com]
Sent: Sunday, March 6, 2022 10:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE IC > 15?

Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1–15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7Csmetz3%40gmu.edu%7Ce7d33597cb63465d355808d9ff8466c4%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637821766401766103%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=87%2BUdZukaha2fWu49Kw7EdyflfFJJTluGpn6D7xKIQc%3Dreserved=0
>
> --
> 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: ESPIE IC > 15?

2022-03-06 Thread Joe Monk 
Looks like as of z/OS 2.3.

2.2 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1–15 and 17.

2.3 doc:

If a program interruption occurs, the SPIE/ESPIE exit receives control only
when all of the following conditions exist:

   - The interrupted program is a problem state program.
   - The program interrupt code is in the range 1 - 15.

Joe

On Sun, Mar 6, 2022 at 8:04 AM Seymour J Metz  wrote:

> When did ESPIE stop supporting interrupt code 17?
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> --
> 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

Job submission from CMS to MVS

2022-03-06 Thread Seymour J Metz 
There are two obvious way to submit an MVS job from CMS:

 1. Spool it ti RSCS and let it go in via NJE

 2. Spool it to a virtual reader on MVS

I'm curious as to how many shops do which, and how they're configured.



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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

Re: JES2 DUPL_JOB parameter

2022-03-06 Thread Joel C. Ewing 
Back in olden days there was a RDINUM JES2 parameter specifying max 
number of Internal Readers, and I believe it was a fairly low value 
(less than 5 as I recall on our initial MVS/XA system in the 1980's), 
either the default or recommended value at the time.  I remember having 
to increase that value over the years, and I think the default was 
eventually increased as well.   That RDINUM parameter seems to have 
since disappeared with no current equivalent.


That suggests that the original reasons for putting a fixed limit on the 
number of concurrent internal readers are no longer valid. and that 
whatever internal JES2 resources an internal reader now requires may be 
dynamically allocated rather than coming from some fixed pool.


The timing issues with single vs multiple C/Is are un-related to 
internal readers, just with concurrent paths to the  JES2 input 
queues.   Would potentially be an issue under VM where z/OS thinks it 
has multiple physical card readers as well.


    Joel C. Ewing

On 3/4/22 10:06, Paul Gilmartin wrote:


On Fri, 4 Mar 2022 08:29:44 -0600, Joel C. Ewing wrote:


Note also that it has been mentioned before in this forum in other
contexts: submitting two jobs with the same job name in sequence and
expecting "DELAY" to force them to run in the sequence submitted is only
valid if you have a single JES2 Converter//I/nterpreter running, which I
suspect is no longer true at most installations.


Does each SYSOUT(,INTRDR) get a separate C/I?  I was told at one
time to use INTRDR sparingly; it used a scarce resource.  But, later,
that such a constraint had been relaxed.


--
Joel C. Ewing

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

ESPIE IC > 15?

2022-03-06 Thread Seymour J Metz 
When did ESPIE stop supporting interrupt code 17?

-- 
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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