Re: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Paul Gilmartin
On Wed, 20 Sep 2023 17:30:05 -0500, Mark Zelden wrote:

>On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen 
> wrote:
>
>Code page issue on your emulator?   Note the valid codes from help when I 
>tried 
>a bracket.  This is z/OS 2.5.  
>
It's EBCDIC, y'know.

-- 
gil

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


Re: SCHEDIRB getting real close showing the code

2023-09-20 Thread Joseph Reichman
It didn’t seem to work that way 

Ep= didn’t equal RBEPA 
RBEPA documented in the data areas Manuel 
At location +C from RBBASIC say entry point of irb routine 

in fact the last digit was odd 
The cirb is running amode 31 

I’ll re-read again 

But and set a breakpoint after the the cirb 

And look at the IRB it built 

Thanks 

> On Sep 20, 2023, at 8:06 PM, Michael Stein  wrote:
> 
> On Wed, Sep 20, 2023 at 06:00:06PM -0400, Joseph Reichman wrote:
>> I decided to use the CIRB macro so that way I could build my own IRB 
>> 
>>  The problem seems to be the AMODE of my RBOPSW is 24 so the high order
>> byte of my rbepa gets chopped off 
> 
> RPEPA doesn't belong to you, you should not touch it. 
> 
> You specified EP= so thats the entry point the IRB will be set
> up to use.
> 
> AMODE=CALLER specifies the AMODE for the routine to be run by the IRB
> routine.  What AMODE is the caller of CIRB running in?
> 
> Go read the CIRB desscription and pay attention to interactions of the
> various operands.
> 
>> 8 *   
>> 9  CIRB EP=IRBADD,   X
>> 0SVAREA=YES, X
>> 1KEY=SUPR,   X
>> 2MODE=SUPR,  X
>> 3RETIQE=YES, X
>> 4STAB=DYN,   X
>> 5WKAREA=255, X
>>RETRN=YES,  X
>>AMODE=CALLER 
> 
> As noted by a prevous poster XR R15,R14 won't usually clear R15.
> 
>> XR   R15,R14   
> 
> --
> 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: SDSF and JESSPOOL

2023-09-20 Thread Michael Babcock
We did not previously convert this one pack rescue system to SDSF external
security.  This is the first time IPLing it with z/OS 2.5.   I defined the
GROUP.SYSPROG.* profile in SDSF, refreshed the SDSF class, made the
necessary ISFPRMxx member and refreshed SDSF.   I could not browse any
output in SDSF.  I had to activate JESSPOOL and define the appropriate
profiles before I could browse output.

The migration guide says JESSPOOL is optional but it appeared it’s not.

On Wed, Sep 20, 2023 at 1:55 PM Radoslaw Skorupka <
0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote:

> W dniu 20.09.2023 o 19:49, Michael Babcock pisze:
> > We have a rescue system that we just brought up on z/OS 2.5.   I
> > couldn't access SDSF so I defined the appropriate groups, modified
> > ISFPRMxx and restarted SDSF, logged off and back on.  I could then get
> > into SDSF.  I could NOT access ANY output whatsoever.  I kept getting
> > NO DISPLAYABLE DATA.  We did not have the JESSPOOL class active on
> > that system.  Now the SDSF security migration guide says that JESSPOOL
> > class activation is not REQUIRED, but until I activated that class, I
> > could not access any output.   Is the book wrong or did I have
> > something not quite set right?
>
> Do you have any definitions in SDSF class?
> Hint: look for GROUP.**
>
>
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
> --
> 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: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Tom Brennan
Also check the terminal type in the ISPF settings.  I usually recommend 
option 3 (3278).  Things like option 5 (3290A) start sending graphic 
escape characters for things like ] and can be confusing.  Not sure how 
this would relate to ! though.  But maybe it's worth a quick look.


On 9/20/2023 3:30 PM, Mark Zelden wrote:

On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen 
 wrote:


It seems like the IPCS 64 bit follow pointer has become ] (right bracket)
instead of ! (exclamation point).



Code page issue on your emulator?   Note the valid codes from help when I tried
a bracket.  This is z/OS 2.5.


ASID(X'013C') ADDRESS(00.) STORAGE --
Command ===>
Valid codes: L, H, %, ?, !
0020   7000   7000   7000   7000
0040            00FD7FE0
0060.:7F. LENGTH(X'20')--All bytes contain X'00'
0080      1004   00020078   00040016
00A0   FE01         1FEDE400
00C0   2800      FBFB   FE7C
00E0.:FF. LENGTH(X'20')--All bytes contain X'00'



Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html

--
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: SCHEDIRB getting real close showing the code

2023-09-20 Thread Michael Stein
On Wed, Sep 20, 2023 at 06:00:06PM -0400, Joseph Reichman wrote:
> I decided to use the CIRB macro so that way I could build my own IRB 
> 
>   The problem seems to be the AMODE of my RBOPSW is 24 so the high order
> byte of my rbepa gets chopped off 

RPEPA doesn't belong to you, you should not touch it. 

You specified EP= so thats the entry point the IRB will be set
up to use.

AMODE=CALLER specifies the AMODE for the routine to be run by the IRB
routine.  What AMODE is the caller of CIRB running in?

Go read the CIRB desscription and pay attention to interactions of the
various operands.

> 8 *   
> 9  CIRB EP=IRBADD,   X
> 0SVAREA=YES, X
> 1KEY=SUPR,   X
> 2MODE=SUPR,  X
> 3RETIQE=YES, X
> 4STAB=DYN,   X
> 5WKAREA=255, X
> RETRN=YES,  X
> AMODE=CALLER 

As noted by a prevous poster XR R15,R14 won't usually clear R15.

>  XR   R15,R14   

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


Re: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Mark Zelden
On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen 
 wrote:

>It seems like the IPCS 64 bit follow pointer has become ] (right bracket)
>instead of ! (exclamation point).
>

Code page issue on your emulator?   Note the valid codes from help when I tried 
a bracket.  This is z/OS 2.5.  


ASID(X'013C') ADDRESS(00.) STORAGE --
Command ===> 
Valid codes: L, H, %, ?, !   
0020   7000   7000   7000   7000 
0040            00FD7FE0 
0060.:7F. LENGTH(X'20')--All bytes contain X'00' 
0080      1004   00020078   00040016 
00A0   FE01         1FEDE400 
00C0   2800      FBFB   FE7C 
00E0.:FF. LENGTH(X'20')--All bytes contain X'00' 



Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html

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


SCHEDIRB getting real close showing the code

2023-09-20 Thread Joseph Reichman
Hi 

I decided to use the CIRB macro so that way I could build my own IRB 

  The problem seems to be the AMODE of my RBOPSW is 24 so the high order
byte of my rbepa gets chopped off 

So here is my IRB entry from SDUMP

IRB: 008AC7A8  
   KEYSTA... 0CWLIC. 00040011  EPA.. 9FF01E80  
   OPSW. 070C  00F01E80LINK. 008FFF98  
   

As you can clearly the first byte of program EPA is getting chopped off in
the RBOPSW

Here is the code that produced this 

 

1 *   
2  L R4,PSAAOLD   
3  USING ASCB,R4  
4  L R4,ASCBASXB  
5  DROP  R4   
6  USING ASXB,R4  
7  L R4,ASXBFTCB  
8 *   
9  CIRB EP=IRBADD,   X
0SVAREA=YES, X
1KEY=SUPR,   X
2MODE=SUPR,  X
3RETIQE=YES, X
4STAB=DYN,   X
5WKAREA=255, X
RETRN=YES,  X
AMODE=CALLER 
 *   
  USING RBBASIC,R1   
  LAR5,IRBPTR
  O R5,=X'8000'  
  STR5,RBEPA 
  OIRBOPSWA,RBOPSW31   Set the amode 
  L R5,RBNEXAV   
  USING IQESECT,R5   
  STR5,IQEADD
  STR1,IQEIRB
  LAR15,PLIST
  STR15,IQEPARAM 
  STR4,IQETCB
*   
 SETLOCK OBTAIN,TYPE=LOCAL,MODE=UNCOND,REGS=SAVE
*   
*   
*   
 SCHEDIRB IQEPTR=IQEADD,   X
   MF=(E,IRBLST)
 SETLOCK RELEASE,TYPE=LOCAL,REGS=SAVE   
*   
*   
 LR13,4(,R13)   
 XR   R15,R14   
 LR14,12(R13)   
 LM   R0,R12,20(R13)
 BR   R14   


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


Re: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Charles Hardee
I'm on 2.5 and just used ! today.


On Wed, Sep 20, 2023 at 3:20 PM Binyamin Dissen 
wrote:

> You specify the pointer type in the storage display screen.
>
> % = 24bit
> ? = 31 bit
>
> On Wed, 20 Sep 2023 15:15:28 -0500 Paul Gilmartin
> <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
>
> :>On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen wrote:
> :>
> :>>It seems like the IPCS 64 bit follow pointer has become ] (right
> bracket)
> :>>instead of ! (exclamation point).
> :>>
> :>How does it distinguish 24- from 31-bit pointers?
> :>Of course that could be resolved with control area maps.
>
> --
> Binyamin Dissen 
> http://www.dissensoftware.com
>
> Director, Dissen Software, Bar & Grill - Israel
>
> --
> 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: JCL symbols used to define other JCL symbols [was: RE: Is SMP/E needed for installs?]

2023-09-20 Thread Phil Smith III
Farley, Peter wrote:
>I believe that statement in the JCL Reference is in error and needs to
>be deleted or at the very least completely rewritten. My quite
>substantial experience using this technique over the last 10-15 years
>is that using JCL symbols as part of the definition of other JCL
>symbols works flawlessly every time. There is no unpredictability. If
>the symbol used to define one symbol isn't already defined, you get
>the literal "" value that you coded as part of the definition.
>This works for both SET and PROC and EXEC statements, without any
>failures or unpredictability that I have ever seen. The resulting
>VALUE of that symbol may cause errors, but there is no
>unpredictability to the symbol definition process.

>I cannot imagine any circumstance in which the result of defining one
>JCL symbol using another JCL symbol would ever be unpredictable.

>If there is any possible case where the result is unpredictable, IBM
>should be required to specify the circumstances and explain why.

I'd bet large coin that what this really means is "If you do this, you're 
likely to confuse yourself". As indeed you COULD-anyone who's gotten sloppy 
with Rexx stemmed variables (where this kind of usage is more common) has been 
burned that way! Of course in the examples Peter Hannigan provided, you're 
*trying* to play those games, so I think it's as safe as anything.


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


Re: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Binyamin Dissen
You specify the pointer type in the storage display screen.

% = 24bit
? = 31 bit

On Wed, 20 Sep 2023 15:15:28 -0500 Paul Gilmartin
<042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

:>On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen wrote:
:>
:>>It seems like the IPCS 64 bit follow pointer has become ] (right bracket)
:>>instead of ! (exclamation point).
:>>
:>How does it distinguish 24- from 31-bit pointers?
:>Of course that could be resolved with control area maps.

--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

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


Re: When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Paul Gilmartin
On Wed, 20 Sep 2023 22:45:29 +0300, Binyamin Dissen wrote:

>It seems like the IPCS 64 bit follow pointer has become ] (right bracket)
>instead of ! (exclamation point).
>
How does it distinguish 24- from 31-bit pointers?
Of course that could be resolved with control area maps.

-- 
gil

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


Re: Softcapping - how to recognize

2023-09-20 Thread DAL POS Raphael
Hi Radoslaw, 

You can use SYSEVENT REQLPDAT to find out about the capping status of a system 
in real time.

See :  

https://www.ibm.com/docs/en/zos/2.3.0?topic=event-obtain-data-defined-capacity-reqlpdat

Ciao, 

-Message d'origine-
De : IBM Mainframe Discussion List  De la part de 
Radoslaw Skorupka
Envoyé : mercredi 20 septembre 2023 20:53
À : IBM-MAIN@LISTSERV.UA.EDU
Objet : Softcapping - how to recognize

I'm looking how to find out (programatically) the LPAR is being softcapped.
AFAIK it was quite easy in CMF, however RMF does not show it explicitly.
I also tried BCPii with no result.

Any clue?

--
Radoslaw Skorupka
Lodz, Poland

--
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


z/OS ServerPac Ordering and Installing - Report from the Front Lines

2023-09-20 Thread Tom Longfellow
I am posting this as a heads up for longtime sysprogs so that they do not have 
to go through what I going through today.

I did my due diligence and reading.  Somehow I either missed or it was not 
readily apparent the RMF has gone through a licensing and marketing  product 
realignment surgery.
The old product RMF has been split into RMF Reporting and z/OS Advanced Data 
Gatherer.   
To achieve the functions that we are paying for with RMF, we now get to buy the 
'entitled'  ADG.   Otherwise ADG is another cost feature.

Sort of like a Car dealer who says:  "You have made a great purchase there.  
Now, would you like buy the engine that runs it?"
Marketing and Licensing at IBM do not seem in touch with the customer who has 
to actually USE the product.
=-=-=-=
My recovery plan is to just order the new FMID as a CBPDO.

Feel free to learn from my failings and save extra installs.

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


When did the IPCS follow 64 bit pointer character change?

2023-09-20 Thread Binyamin Dissen
It seems like the IPCS 64 bit follow pointer has become ] (right bracket)
instead of ! (exclamation point).

--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

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


Re: Softcapping - how to recognize

2023-09-20 Thread Sri h Kolusu
>> I'm looking how to find out (programatically) the LPAR is being softcapped.

Check this 

https://groups.google.com/g/bit.listserv.ibm-main/c/ZAMY8URyeTw

Thanks,
Kolusu

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


Re: Softcapping - how to recognize

2023-09-20 Thread Charles Mills
Does this help?

/* Point to the RMF data */
CVT_addr = Storage('10', 4) 
  
RMCT_addr = StorageCO(CVT_addr, 604, 4) 
  
RCT_addr = StorageCO(RMCT_addr, 228, 4) 
  

MSUString:
/* Return either "(R4HA=nn, CAPPED!)" or "(R4HA=nn, not capped)" */
RCTIMGWU = C2D(StorageCO(RCT_addr, 28, 4))  

RCTLACS = C2D(StorageCO(RCT_addr, 196, 4))  


RetData = "(R4HA=" || RCTLACS || ", "
If RCTLACS >= RCTIMGWU Then RetData = RetData || "CAPPED!)"
Else RetData = RetData || "not capped)"
Return RetData

Charles

On Wed, 20 Sep 2023 20:53:11 +0200, Radoslaw Skorupka  
wrote:

>I'm looking how to find out (programatically) the LPAR is being softcapped.
>AFAIK it was quite easy in CMF, however RMF does not show it explicitly.
>I also tried BCPii with no result.

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


Re: SDSF and JESSPOOL

2023-09-20 Thread Radoslaw Skorupka

W dniu 20.09.2023 o 19:49, Michael Babcock pisze:
We have a rescue system that we just brought up on z/OS 2.5.   I 
couldn't access SDSF so I defined the appropriate groups, modified 
ISFPRMxx and restarted SDSF, logged off and back on.  I could then get 
into SDSF.  I could NOT access ANY output whatsoever.  I kept getting 
NO DISPLAYABLE DATA.  We did not have the JESSPOOL class active on 
that system.  Now the SDSF security migration guide says that JESSPOOL 
class activation is not REQUIRED, but until I activated that class, I 
could not access any output.   Is the book wrong or did I have 
something not quite set right?


Do you have any definitions in SDSF class?
Hint: look for GROUP.**



--
Radoslaw Skorupka
Lodz, Poland

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


Softcapping - how to recognize

2023-09-20 Thread Radoslaw Skorupka

I'm looking how to find out (programatically) the LPAR is being softcapped.
AFAIK it was quite easy in CMF, however RMF does not show it explicitly.
I also tried BCPii with no result.

Any clue?

--
Radoslaw Skorupka
Lodz, Poland

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


Re: SDSF and JESSPOOL

2023-09-20 Thread Steve Beaver
SDSF is SAF controlled 

Sent from my iPhone

No one said I could type with one thumb 

> On Sep 20, 2023, at 12:49, Michael Babcock  wrote:
> 
> We have a rescue system that we just brought up on z/OS 2.5.   I couldn't 
> access SDSF so I defined the appropriate groups, modified ISFPRMxx and 
> restarted SDSF, logged off and back on.  I could then get into SDSF.  I could 
> NOT access ANY output whatsoever.  I kept getting NO DISPLAYABLE DATA.  We 
> did not have the JESSPOOL class active on that system.  Now the SDSF security 
> migration guide says that JESSPOOL class activation is not REQUIRED, but 
> until I activated that class, I could not access any output.   Is the book 
> wrong or did I have something not quite set right?
> 
> --
> 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


SDSF and JESSPOOL

2023-09-20 Thread Michael Babcock
We have a rescue system that we just brought up on z/OS 2.5.   I 
couldn't access SDSF so I defined the appropriate groups, modified 
ISFPRMxx and restarted SDSF, logged off and back on.  I could then get 
into SDSF.  I could NOT access ANY output whatsoever.  I kept getting NO 
DISPLAYABLE DATA.  We did not have the JESSPOOL class active on that 
system.  Now the SDSF security migration guide says that JESSPOOL class 
activation is not REQUIRED, but until I activated that class, I could 
not access any output.   Is the book wrong or did I have something not 
quite set right?


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


Re: Will AI free Bill Johnson? (was AI will surpass human intelligence!)

2023-09-20 Thread Michael Oujesky

I presume you have a copy of Faster Than Thought.

Michael

At 01:09 PM 9/17/2023, Bernd Oppolzer wrote:

Content-Transfer-Encoding: 8bit

I'd really be interested, because I am collecting historic computer 
related books,


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


Re: z/OS 3.1 Announcement - Helpful links

2023-09-20 Thread Albertus de Wet
Marna

If my memory assists me well, I heard during the last SHARE in NOLA, that
z/OS 3.1 will be available for ordering on 9/19 and available for delivery
on 9/29.
I tried to place a software upgrade order on IBM, but only 2.5 is listed. -
I assume since it's a new version, there will be cost implications.

Can you perhaps point me in the right direction to start the ordering
process, please?

Thank you
Bert


On Tue, Aug 8, 2023 at 8:49 AM Marna WALLE  wrote:

> The z/OS 3.1 GA Announcement is available for your reading pleasure!
> https://www.ibm.com/docs/en/announcements/zos-31-availability
>
> Some significant points to note:
> -   Planned availability date is September 29, 2023.  Since this is a
> new z/OS version, there is a new program number, 5655-ZOS.
> -   PLEASE read carefully the IBM Semeru (Java) dependency in the
> announcement letter.
> -   Many of the new functions in z/OS 3.1 have an associated IBM
> Education Assistant Module, which you can find here:
> https://github.com/IBM/IBM-Z-zOS/tree/main/zOS-Education/zOS-3.1-Education
> Each of these PDF files focus on a specific function and can quickly show
> you the technical information you would need.
> -   The z/OS 3.1 Planning for Installation book is available right now
> to start your planning,
> https://www.ibm.com/docs/en/SSLTBW_2.5.0/pdf/e0zb100_v3r1.pdf.
> -   The z/OS 3.1 Upgrade Workflow is also available in a PTF to start
> your upgrade evaluation. See
> https://www.ibm.com/docs/en/zos/2.5.0?topic=level-zos-upgrade-workflow
> (It was provided on the z/OS V2.5 System Level web page, as we do not yet
> have the z/OS 3.1 books on IBM Documentation, except for the z/OS 3.1
> Planning for Installation.) Another PTF is planned after GA when the z/OS
> 3.1 books are available, so that the links in the Workflow point to the
> latest books.  The exported format of that post-GA z/OS 3.1 Upgrade
> Workflow will be put on the web at that time.  I strongly recommend using
> the “native” z/OSMF Workflow now rather than the export to help assess
> which upgrade steps are applicable to your system easily.
>
> Also – you might want to also look at an associated standalone product, AI
> System Services for IBM z/OS 1.1,
> https://www.ibm.com/docs/en/announcements/ai-system-services-zos?region=US
> which was also announce today.
>
> Happy reading!
>
> --
> 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: Test site for certificate revocation?

2023-09-20 Thread Charles Mills
@Colin, I can do that. That may be one of the better options.

Thanks all.

Charles

On Wed, 20 Sep 2023 08:22:22 +0100, Colin Paice  wrote:

>You could try openssl s_server
>I use this script on Linux
>
>
>*cert=" -cert ./docec384.pem -certform pem -key docec384.key.pem -keyform
>pem" CA="-chainCAfile ./docca256.pem"*
>*debug="-trace "*
>*port="-port 4433 "*
>*openssl s_server $port $cert  $CA $debug -www  *

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


Re: JCL symbols used to define other JCL symbols [was: RE: Is SMP/E needed for installs?]

2023-09-20 Thread Paul Gilmartin
Thanks for changing the Subject: as the topic drifted.

On Wed, 20 Sep 2023 15:23:31 +, Farley, Peter wrote:

>I believe that statement in the JCL Reference is in error and needs to be 
>deleted or at the very least completely rewritten.  My quite substantial 
>experience using this technique over the last 10-15 years is that using JCL 
>symbols as part of the definition of other JCL symbols works flawlessly every 
>time.  ...
>
The Ref. is inconsistent in its terminology:

The SET statement contains one or more parameters:
symbolic-parameter=value[,symbolic parameter=value]...

clearly in:
>On Wed, 20 Sep 2023 04:12:20 +, Peter Hannigan wrote:
>>...
>>// SET A=' '
>>
Peter H. was specifying a symbol within a "symbolic-parameter",
not within the "value"
>
>
>  - Do not specify JCL symbols within other JCL symbols. The results
>can be unpredictable, especially if the imbedded JCL symbol is
>not previously defined.
>
For clarity, that should have said "symbolic-parameter", which
I assume was within its intended meaning, not simply "JCL
symbols within"

Regardless, I agree with both Peter F. and Peter H. that either
construct works provided that all  symbols are resolved according
to "Determining equivalent JCL" which should be cited here
unless it can be assumed to apply consistently throughout the Ref.

-- 
gil

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


JCL symbols used to define other JCL symbols [was: RE: Is SMP/E needed for installs?]

2023-09-20 Thread Farley, Peter
I believe that statement in the JCL Reference is in error and needs to be 
deleted or at the very least completely rewritten.  My quite substantial 
experience using this technique over the last 10-15 years is that using JCL 
symbols as part of the definition of other JCL symbols works flawlessly every 
time.  There is no unpredictability.  If the symbol used to define one symbol 
isn’t already defined, you get the literal “” value that you coded as part 
of the definition.  This works for both SET and PROC and EXEC statements, 
without any failures or unpredictability that I have ever seen.  The resulting 
VALUE of that symbol may cause errors, but there is no unpredictability to the 
symbol definition process.

I cannot imagine any circumstance in which the result of defining one JCL 
symbol using another JCL symbol would ever be unpredictable.

If there is any possible case where the result is unpredictable, IBM should be 
required to specify the circumstances and explain why.

Peter

P.S. – I will add that all of my experience using symbols to define other 
symbols also uses EXPORT SYMLIST=* as a standard part of JCL and 
SYMLIST=JCLONLY for in-stream DD’s with symbols to be substituted.

From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Wednesday, September 20, 2023 9:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is SMP/E needed for installs?


On Wed, 20 Sep 2023 04:12:20 +, Peter Hannigan wrote:

>...

>// SET A=' '

>



  - Do not specify JCL symbols within other JCL symbols. The results

can be unpredictable, especially if the imbedded JCL symbol is

not previously defined.



Damn feckless IBM!  Don't call a construct "unpredictable".  Either

report it as a JCL error or specify the effect in the Ref.



But ISVs should avoid "unpredictable" constructs in customer-facing code.



--



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


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


Re: Why it's important to take Seymour's advice

2023-09-20 Thread Peter Relson
Adam J wrote

Given the proper authorization, you can:

- Issue an AXSET, specifying a value of 1
- Issue an SSAR instruction identifying the target address space as the 
secondary address space
- Use MVCP / MVCS instructions to copy data between your primary address space 
and the secondary address space



While that is "true" (aside from the fact that SSAR would be rejected if this 
is a reusable ASID and would need to be SSAIR),
this is not something you should do. And your "connection" could break at any 
instant unless the target address space is both non-swappable and not 
memtermable.

Adam J wrote

There is also the technique of using the special ALET value of x'0001' and 
using AR mode to reference data from another address space.


That too is a bad idea unless you have addressability to this other space as 
your "secondary" address space (which typically would be after a space-switch 
PC to "you").

z/OS does not support the concept of "address space faults" (i.e., the program 
check you get when referencing storage in another address space when that 
address space is swapped out).  This is one of the reasons why cross-memory 
servers are required to be in non-swappable address spaces.

Peter Relson
z/OS Core Technology Design


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


Re: Why it's important to take Seymour's advice

2023-09-20 Thread Tom Marchant
No. z/Architecture, as well as System/360, 370 and 390 have consistently 
numbered bits from left to right. 

You would do well to read, very carefully,
https://d.cxcore.net/Eric%20S%20Raymond/How%20To%20Ask%20Questions%20The%20Smart%20Way.pdf

-- 
Tom Marchant

On Wed, 20 Sep 2023 07:57:05 -0400, Joseph Reichman  
wrote:

>Bit 0 would be if I did this O  R5,=X’0001’
>
>> On Sep 19, 2023, at 9:33 PM, Seymour J Metz  wrote:
>> 
>> That's bit 0.
>> 
>> 
>> From: IBM Mainframe Discussion List  on behalf of 
>> Joseph Reichman 
>> Sent: Tuesday, September 19, 2023 9:20 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Why it's important to take Seymour's advice
>> 
>> I have a O R5,=X’8000’
>> To set bit 31

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


Re: Is SMP/E needed for installs?

2023-09-20 Thread Phil Smith III
Peter Hannigan wrote:
>If the length of the prefix can be limited to seven characters then
>this can be used:


Wow. It took me 10+ minutes of staring at this to puzzle it out. Too clever by 
half for me (and that's not meant as an insult). 

After much discussion, we've concluded that nobody is going to load our stuff 
to the "root" on a real system, and if they do, then they're going to be an 
SMP/E jock already. So while I love this suggestion and will look at other ways 
to use it, I think I'm just going to put a comment in the common member that 
does the SETs saying "You can't have a null HLQ/RPREFIX". The other places 
where the HLQ gets substituted in would have the same problem (though, yes, I 
could be clever and set them with a trailing do, but that way lies madness).

I really appreciate all the help folks have provided with this. Our 
installation is now MUCH cleaner/simpler because the edits to the actual jobs 
comprise just:

1.  JOB card (doh)
2.  JCLLIB (right below the JOB card, so easy to find)
3.  Possibly SMS changes from UNIT= and VOL=SER=



I vaguely considered changing the last one to use a variation on your approach, 
Peter, but that would have to assume (as the default does) that all the data 
sets use the same values. Again, at that point, hopefully the customer is 
sophisticated enough to deal with it; can only hold their hands so far before 
it becomes ridiculous.

If folks think I'm being silly in any of these conclusions, I'd love to hear it!

...phsiii


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


Re: z/OSMF and Zowe

2023-09-20 Thread Matt Hogstrom
I think that it comes down to provenance (is where it came from trusted) as 
well as a need for support when something goes wrong.  The community support is 
best effort with no warranties.  Other vendors like IBM, Rocket and Broadcom 
are now pre-requing the Zowe and as such they provide support and the customer 
downloads the package from the vendor.  At least for Broadcom, it’s the same 
package as distributed by the Zowe community but most large Z shops won’t even 
let you access the site.

I was on the customer side of the fence for many years and no one wants to say 
that the thing I’m using came from OpenSource if there is an issue.  We want 
someone to call at 0-dark-thirty when things go wrong.  I’m not sure that this 
requirement has changed.  I think that’s the same issue with the Rocket and 
other ports of common Linux tools although I think those are less impactful to 
production for the most part.  In our world, outages come with post-mortems. 

Matt Hogstrom

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom



> On Sep 20, 2023, at 3:12 AM, Robin Atwood  wrote:
> 
> Thanks, Brian and Matt. Perhaps the fact that you can get Zowe directly from 
> IBM will help mitigate the prejudice against open source!


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


Re: Is SMP/E needed for installs?

2023-09-20 Thread Paul Gilmartin
On Wed, 20 Sep 2023 04:12:20 +, Peter Hannigan wrote:
>...
>// SET A=' '
>

  - Do not specify JCL symbols within other JCL symbols. The results
can be unpredictable, especially if the imbedded JCL symbol is
not previously defined.

Damn feckless IBM!  Don't call a construct "unpredictable".  Either
report it as a JCL error or specify the effect in the Ref.

But ISVs should avoid "unpredictable" constructs in customer-facing code.

-- 
gil

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


Re: Why it's important to take Seymour's advice

2023-09-20 Thread Joseph Reichman
Bit 0 would be if I did this O  R5,=X’0001’

> On Sep 19, 2023, at 9:33 PM, Seymour J Metz  wrote:
> 
> That's bit 0.
> 
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Joseph Reichman 
> Sent: Tuesday, September 19, 2023 9:20 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Why it's important to take Seymour's advice
> 
> I have a O R5,=X’8000’
> To set bit 31
> 
> Not home now but I’ll look up and check the SCHEDIRB again
> 
> Get Outlook for iOS
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Seymour J Metz 
> Sent: Tuesday, September 19, 2023 9:07:18 PM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: Why it's important to take Seymour's advice
> 
>> 
> As it was recommended to issue SCHEDIRB From an IRB I issue it from a STIMER 
> routine
> 
> The devil is in the details. As coded that does not apply.
> 
>>   SVAREA=YES,
>>   MODE=SUPR,
> 
> One or the other but not both.
> 
>> XR   R15,R14
> 
>  XR   R15,R15
> 
> Your choice of names and your comments are confusing; IRBPTR is code, not a 
> pointer, and you're not doing anything with an RB when the comment says 
> "Chain rb pointer to put this IRB as next".
> 
> Note: if you really need the exit to get control in SM then you shouldn't 
> save the registers. The manual spells that out.
> 
> That said, I don't see what's setting bit 31.
> 
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Joseph Reichman 
> Sent: Tuesday, September 19, 2023 8:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Why it's important to take Seymour's advice
> 
> Here it is
> 
> As it was recommended to issue SCHEDIRB From an IRB I issue it from a STIMER 
> routine
> 
> I'll start with the STIMERM I use STIMERM as opposed to STIMER because it 
> lets my pass a parameter (which is the save area for 13)
> 
> STIMERM SET,  X
>   ID=TIMER,   X
>   BINTVL=NOW, X
>   ERRET=ERROR,X
>   EXIT=STIMER,X
>   PARM=TIMER_PLIST,   X
>   WAIT=NO,MF=(E,TIMERLST)
> 
> 
> STIMER   DS   0D
>  STM  R14,R12,12(R13)
> *
>  LRR4,R15
>  DROP  R3
>  USING STIMER,R4
>  LRR10,R13
>  L R13,4(,R1)Get Save area
>  DROP  R13
>  USING TIMERSVE,R13
>  STR10,4(R13)
> *
>  SETLOCK OBTAIN,TYPE=LOCAL,MODE=UNCOND,REGS=SAVE
> *
> *
> *  Chain rb pointer to put this IRB as next
> *
>  LAR5,IRBPTR
>  O R5,=X'8000'
>  STR5,IRBADD
>  L R6,PSATOLD
>  USING TCB,R6
>  L R6,TCBJSTCB   Get the Job Step tcb
>  STR6,JSTCB
>  SCHEDIRB EPPTR=IRBADD,X
>TCBPTR=JSTCB,   X
>SVAREA=YES, X
>MODE=SUPR,  X
>KEY=SUPR,   X
>PARAMPTR=PLIST, X
>MF=(E,IRBLST)
>  SETLOCK RELEASE,TYPE=LOCAL,REGS=SAVE
> *
> *
>  LR13,4(,R13)
>  XR   R15,R14
>  LR14,12(R13)
>  LM   R0,R12,20(R13)
>  BR   R14
>  DROP  R13
>  USING WORKAREA,R13
>  DROP  R4
> IRBPTR   DS0D
> *
>  STM  R14,R12,12(R13)
>  LRR5,R15
>  USING IRBPTR,R5
>  LRR10,R1Save Plist pointer
>  LOAD  EP=GETVECT
>  STR0,0(R10) Store Pointer
>  XRR15,R15
>  L R14,12(R13)
>  LMR0,R12,20(R13)
>  BRR14
>  DROP  R5
> 
> 
> WORKAREA DSECT
> SAVEAREA DS 18F
> TIMERSVE DS 18F
>  DS 0D
> TIMERDSF
> PARMPTR  DSA
> FADDRDSA
> DEPARM   DESERV MF=L
> CSVLMPEA DSCL(LPMEA_LEN)
> DELENEQU   *-DEPARM
>  SCHEDIRB MF=(L,IRBLST)
>  CSVQUERY MF=(L,CSVQUERY)
> TIMERLST STIMERM SET,MF=L
> PLISTDS0A
>  DSA
> TIMER_PLIST DS  A
> DESPTR   DSA
> IRBADD   DSA
> JSTCBDSA
> T
> T
> T
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Seymour J Metz
> Sent: Tuesday, September 19, 2023 8:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Why it's important to take Seymour's advice
> 
> Show the code.
> 
> 
> From: IBM Mainframe 

Re: SORT INCLUDE problem

2023-09-20 Thread Jack Zukt
Hello Kolusu,

Thank you very much for your help.
I was not quite happy with the solution that I had come up with, as I was
reading the input file twice and that bothered me because that is not an
efficient solution.
You latest solution is much simpler and efficient. And much more elegant as
well.
Thank you once again for all your help
Best wishesJack

On Mon, 18 Sept 2023 at 16:50, Sri h Kolusu  wrote:

> >> Is there a way to get all the dataset profiles that have two different
> groups with the same access using SORT or ICETOOL but without using
> JOINKEYS, so that the input file would only needed to be read once, using
> SORTIN as the DDNAME?
>
> Jack,
>
> That is quite simple.  There is a lot of functionality that DFSORT can
> offer to get the desired results.
>
> So, if your intention is to find the COMMON datasets for ACC of GPRFCICS
> and GPRFSTG, here is a JCL that will give you the desired results.  You
> don't even have to filter out Type 0404 records separately as we can do it
> in a Single pass of data from the raw IRRDBU00 output.
>
> //STEP0100 EXEC PGM=SORT
> //SYSOUT   DD SYSOUT=*
> //SORTDIAG DD DUMMY
> //SORTIN   DD DISP=SHR,DSN=Your.raw.IRRDBU00.output
> //SORTOUT  DD SYSOUT=*
> //SYMNAMES DD *
> ** INPUT TYPE 0404 RECORD LAYOUT **
> TYP,05,04,CH
>T404,C'0404'
> DSN,10,44,CH
> GRP,62,08,SS
>STG,C'GPRFSTG'
>   CICS,C'GPRFCICS'
> ACC,71,08,CH
>   ALTER,C'ALTER'
>READ,C'READ'
> ** REFORMATTED RECORD LAYOUT **
> IN-RDW,01,04,BI
> IN-DSN,*,44,CH
> SKIP,1
> IN-GRP,*,08,CH
> SKIP,1
> IN-ACC,*,08,CH
> SKIP,1
> TP-ACC,*,08,CH
> /*
> //SYSIN DD *
>   OPTION VLSCMP
>   INCLUDE COND=(TYP,EQ,T404,AND,
> ACC,EQ,ALTER,AND,
>(GRP,EQ,STG,OR,
> GRP,EQ,CICS))
>
>INREC BUILD=(IN-RDW,
> DSN,C'|',
> ACC,C'|',
> GRP,C'|')
>
>   SORT FIELDS=(IN-DSN,A,
>IN-ACC,A)
>
>   OUTREC IFTHEN=(WHEN=GROUP,KEYBEGIN=(IN-DSN),
>  PUSH=(TP-ACC:IN-ACC))
>
>   OUTFIL VTOF,
>   BUILD=(IN-DSN),
>   INCLUDE=(IN-ACC,EQ,STG,AND,
>TP-ACC,EQ,CICS)
> /*
>
> Thanks,
> Kolusu
> DFSORT Development
> IBM Corporation
>
>
>
> --
> 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: Test site for certificate revocation?

2023-09-20 Thread Colin Paice
You could try openssl s_server
I use this script on Linux


*cert=" -cert ./docec384.pem -certform pem -key docec384.key.pem -keyform
pem" CA="-chainCAfile ./docca256.pem"*
*debug="-trace "*
*port="-port 4433 "*
*openssl s_server $port $cert  $CA $debug -www  *

and a web browser to https://127.0.0.1:4433

You'll have to use your own certificates and specify the ip address.

If you need more help,please contact me offline and I'll send you my test
certificates and instructions

Colin


On Wed, 20 Sept 2023 at 01:57, Charles Mills  wrote:

> Yes, that should work. However I don't have an appropriate test server.
>
> Yes, I could set one up ...
>
> Charles
>
> On Wed, 20 Sep 2023 10:36:30 +1000, Andrew Rowley <
> and...@blackhillsoftware.com> wrote:
>
> >On 20/09/2023 8:37 am, Charles Mills wrote:
> >> Does anyone know of a server URL that will present a revoked
> certificate (for my testing purposes)?
> >
> >Can you create a certificate for your own test site with Lets Encrypt,
> >then revoke it?
>
> --
> 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: z/OSMF and Zowe

2023-09-20 Thread Robin Atwood
Thanks, Brian and Matt. Perhaps the fact that you can get Zowe directly from 
IBM will help mitigate the prejudice against open source!

Robin

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Brian Westerman
Sent: Wednesday, September 20, 2023 12:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OSMF and Zowe

I believe you can still order CBIPO, but z/OSMF does (unfortunately) seem to be 
the way IBM wants everyone to go.  I personally disagree with z/OSMF for many 
reasons (most of them due to overhead and capability restrictions), but mine 
seems to be a waste of breath.  :)

Any way ZOWE is open source, and many shops won't allow that.  It's actually a 
pretty good idea, but still some shops see open source as inherently evil. 

Brian

--
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