Google Paris datacenter down 2 weeks, no word on restore

[Mike Schwab]

https://www.theregister.com/2023/05/10/google_cloud_paris_outage_persists/



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Solarwind to z/OS

[Jake Anderson]

Hello Tom

So the solarwind expects SNMPV2 ? Does SNMPV2 handle bulk request?



On Tue, May 9, 2023, 11:22 PM Tom Longfellow <
03e29b607131-dmarc-requ...@listserv.ua.edu> wrote:

> My experiences with Solarwinds interacting with z/OS have not been
> pleasant.
>
> First discovered it as my major source of Scanning ports of my system for
> vulnerabilities.Until I purposely put in Defensive Management Demon
> filters, they were my ONLY source of that kind of hacking attempts.  Maybe
> it was a different program on the server identifying itself as Solarwinds,
> but a bad tase is a bad taste.
>
> Second discovery is that their software introduced  worldwide
> investigations into some questionable practices and intrusion attempts.
>  Defective software or Chinese TikTok attack V1.0.
>
> That was enough to keep them in mind as a company to avoid. If they
> have cleaned up their game, more power to them.  If I have misread the
> situation, I apologize.  I have enough worries before trusting something
> with the track record I have experienced.
>
> --
> 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: XLC version? [was: RE: XLC - Weak symbols]

[David Crayford]

2.4.1 is more than a slight update, it’s a completely different front-end. To 
make it more confusing there are three C/C++ compiler products on z/OS.

XL C/C++ is the legacy compiler which supports 31/64-bit and has CICS 
translation built it. It can run as a batch program. IBM have made no 
statements of direction but it’s withering on the vine and does not support the 
latest C/C++ standards. It’s almost impossible to use it for any modern ports. 
I can’t see this product ever disappearing as it’s required for the old school 
JCL only shops. That’s not a dig at Peter, we have products that use PDS data 
sets and are compiled using a legacy SCM product. I find it very difficult to 
adapt when I work on these products after spending so long building
in a shell. 

XL C/C++ 2.4.1 Web Deliverable is a port of Clang which uses the existing 
back-end. It’s better than the legacy compiler but it must run as a z/OS UNIX 
executable. It supports more modern language standards such as C++14. 

Open XL C/C++ is a full on port of Clang. IBM are working with the open source 
community. It’s interesting to read the code reviews which include devs from 
Apple and Google. It’s my understanding that this compiler will replace 2.4.1 
some time in the future.  

> On 9 May 2023, at 12:29 pm, Phil Smith III  wrote:
> 
> David Crayford wrote:
> 
>> They're different products. I can't see a convergence as that would be
> 
>> a high impact change to customers and would require Metal/C spinning
> 
>> off. It's far more likely that XL 2.4.1 and Open XL C/C++ will
> 
>> converge.
> 
> 
> 
> Huh, something gave me the impression that 2.4.1 was Open XL C/C++. The fact 
> that it looks like a slight update to 2.4 of XL C is, of course, a big part 
> of the problem here!
> 
> 
> 
> I would very much like to understand what's what and what's going where here, 
> for planning purposes. IBM? Please?
> 
> 
> --
> 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: JES2 Submitlib Bootstrap problem

[Mark Jacobs]

The point that I'm trying to make with IBM is why support a path option on the 
SUBMITLIB parameter if it just doesn't work during JES2 initialization when the 
system is IPLed? The design is broken.

Mark Jacobs  

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com


--- Original Message ---
On Tuesday, May 9th, 2023 at 5:22 PM, Paul Gilmartin 
<042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:


> On Tue, 9 May 2023 19:58:11 +, Mark Jacobs wrote:
> 
> > I opened a ticket with IBM on this. Should be interesting to hear what they 
> > say.
> 
> Keep the list posted. I'm taking short odds on WAD in view of Rex's concerns.
> OMVS remains a second-class citizen; considered expendable. You might be
> advised to move your submitlib to an old-fashioned PDS.
> 
> > --- Original Message ---
> > On Tuesday, May 9th, 2023 at 12:21 PM, Pommier, Rex wrote:
> > 
> > > I see a problem with this scenario. It appears to me that there is a call 
> > > (not necessarily by Shmuel) to potentially have JES2 wait for OMVS to be 
> > > up before it does its startup (or at least completes the startup). Due to 
> > > a self-inflicted screw-up on one of our LPARs, OMVS decided it had to do 
> > > a filesystem check on every filesystem on the system. This took a good 
> > > half hour where it simply appeared our LPAR was hung. JES2 had come up 
> > > and I was able to start a few address spaces that are dependent on JES so 
> > > I could figure out what was going on. Had JES been waiting for OMVS we 
> > > would have been completely in the dark on this issue.
> > > 
> > > I could see there being communication between JES and OMVS so that when 
> > > OMVS gets initialized it signals JES to redrive any failed zFS 
> > > allocations, but don't force JES to wait until zFS is available.
> 
> 
> --
> 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: JES2 Submitlib Bootstrap problem

[Paul Gilmartin]

On Tue, 9 May 2023 19:58:11 +, Mark Jacobs wrote:

>I opened a ticket with IBM on this. Should be interesting to hear what they 
>say.
>
Keep the list posted.  I'm taking short odds on WAD in view of Rex's concerns.
OMVS remains a second-class citizen; considered expendable.  You might be
advised to move your submitlib to an old-fashioned PDS.


>--- Original Message ---
>On Tuesday, May 9th, 2023 at 12:21 PM, Pommier, Rex wrote:
>
>> I see a problem with this scenario. It appears to me that there is a call 
>> (not necessarily by Shmuel) to potentially have JES2 wait for OMVS to be up 
>> before it does its startup (or at least completes the startup). Due to a 
>> self-inflicted screw-up on one of our LPARs, OMVS decided it had to do a 
>> filesystem check on every filesystem on the system. This took a good half 
>> hour where it simply appeared our LPAR was hung. JES2 had come up and I was 
>> able to start a few address spaces that are dependent on JES so I could 
>> figure out what was going on. Had JES been waiting for OMVS we would have 
>> been completely in the dark on this issue.
>> 
>> I could see there being communication between JES and OMVS so that when OMVS 
>> gets initialized it signals JES to redrive any failed zFS allocations, but 
>> don't force JES to wait until zFS is available.

-- 
gil

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

Re: Can REXX OUTTRAP trap WTO's?

[Farley, Peter]

This would be a one-time call to retrieve the WTO output, not a repeating 
event, but thanks for the suggestion.

Instead I'm coding a test version of the in-house utility to make the data 
easier to get (PUTLINE instead of WTO) for my one-time use.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
David Spiegel
Sent: Tuesday, May 9, 2023 2:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

Hi Peter,
Assuming you  have SDSF, have you considered using its one of its APIs 
to scan the SYSLOG every n minutes?

Regards,
David

On 2023-05-09 13:55, Farley, Peter wrote:
> I believe that the CONSOLE facility is authorized and I have no 
> authorization.  I have no access to either System Rexx or Netview Rexx.
>
> Any other ideas?  The business need is not sufficient to request 
> authorizations, this is just a script to set up some test data that would 
> really be helped by capturing output generated as a WTO by an existing 
> in-house utility program.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Seymour J Metz
> Sent: Tuesday, May 9, 2023 1:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can REXX OUTTRAP trap WTO's?
>
> See the CONSOLE facility in TSO. I don't know whether it is available in 
> System Rexx.
>
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Tuesday, May 9, 2023 1:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can REXX OUTTRAP trap WTO's?
>
> Cross-posted to IBM-MAIN and TSO-REXX lists.
>
> Is there any way for  Rexx script to capture WTO output?  This is a simple 
> case, a one-line WTO, no multiline possible.
>
> I only recently found a need to do this, and my tests so far say "no it 
> can't".
>
> /* Rexx */
> /* Capture WTO from BATCHPGM */
> xtrp = outtrap("zdsp.")
> address attchmvs "BATCHPGM"
> xtrp = outtrap("OFF")
> say "ZDSP.1="zdsp.1
>
> Execution result online in TSO:
>
> *** WTO OUTPUT FROM BATCHPGM ***
> ZDSP.1=ZDSP.1
>
> Peter
--

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: Can REXX OUTTRAP trap WTO's?

[Farley, Peter]

Yes, I guess that would be the only real way to accomplish this.  I could use 
the SDSF Rexx API, but it may be more trouble that it is worth to me for this 
one-time use.

Thanks for the suggestion though.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
ITschak Mugzach
Sent: Tuesday, May 9, 2023 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

If this process run as a batch job, the wto will be written to jesmsglg.
You may call sdsf to read your own job log...

בתאריך יום ג׳, 9 במאי 2023 ב-20:56 מאת Farley, Peter <
031df298a9da-dmarc-requ...@listserv.ua.edu>:

> I believe that the CONSOLE facility is authorized and I have no 
> authorization.  I have no access to either System Rexx or Netview Rexx.
>
> Any other ideas?  The business need is not sufficient to request 
> authorizations, this is just a script to set up some test data that 
> would really be helped by capturing output generated as a WTO by an 
> existing in-house utility program.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discussion List  On 
> Behalf Of Seymour J Metz
> Sent: Tuesday, May 9, 2023 1:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can REXX OUTTRAP trap WTO's?
>
> See the CONSOLE facility in TSO. I don't know whether it is available 
> in System Rexx.
>
> 
> From: IBM Mainframe Discussion List  on 
> behalf of Farley, Peter 
> <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Tuesday, May 9, 2023 1:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can REXX OUTTRAP trap WTO's?
>
> Cross-posted to IBM-MAIN and TSO-REXX lists.
>
> Is there any way for  Rexx script to capture WTO output?  This is a 
> simple case, a one-line WTO, no multiline possible.
>
> I only recently found a need to do this, and my tests so far say "no 
> it can't".
>
> /* Rexx */
> /* Capture WTO from BATCHPGM */
> xtrp = outtrap("zdsp.")
> address attchmvs "BATCHPGM"
> xtrp = outtrap("OFF")
> say "ZDSP.1="zdsp.1
>
> Execution result online in TSO:
>
> *** WTO OUTPUT FROM BATCHPGM ***
> ZDSP.1=ZDSP.1
>
> Peter
--

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: JES2 Submitlib Bootstrap problem

[Mark Jacobs]

I opened a ticket with IBM on this. Should be interesting to hear what they say.

Mark Jacobs 

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com


--- Original Message ---
On Tuesday, May 9th, 2023 at 12:21 PM, Pommier, Rex  
wrote:


> I see a problem with this scenario. It appears to me that there is a call 
> (not necessarily by Shmuel) to potentially have JES2 wait for OMVS to be up 
> before it does its startup (or at least completes the startup). Due to a 
> self-inflicted screw-up on one of our LPARs, OMVS decided it had to do a 
> filesystem check on every filesystem on the system. This took a good half 
> hour where it simply appeared our LPAR was hung. JES2 had come up and I was 
> able to start a few address spaces that are dependent on JES so I could 
> figure out what was going on. Had JES been waiting for OMVS we would have 
> been completely in the dark on this issue.
> 
> I could see there being communication between JES and OMVS so that when OMVS 
> gets initialized it signals JES to redrive any failed zFS allocations, but 
> don't force JES to wait until zFS is available.
> 
> My $.02.
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
> Seymour J Metz
> 
> Sent: Tuesday, May 9, 2023 10:10 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Re: JES2 Submitlib Bootstrap problem
> 
> Yes, IBM absolutely should take startup sequence into account and should 
> provide mechanisms to ensure that things occur in the proper order. This goes 
> beyond OMVS.
> 
> 
> --
> Shmuel (Seymour J.) Metz
> https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!KjMRP1Ixj6eLE0Fj!oLVba7cIWA-HvwL4aaVssbMaEZeCG3m_dnLPJgpEL8DOiFs5DAJaoVf27kYVUZyYy_Nw7UxsOVp6sogwmA$
> 
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu]
> Sent: Tuesday, May 9, 2023 11:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2 Submitlib Bootstrap problem
> 
> On Tue, 9 May 2023 12:18:11 +, Mark Jacobs wrote:
> 
> > I defined several submitlibs in my JES2PARM to use directories in a ZFS 
> > filesystem. When I hotstart JES2, JES2 can find everything and is happy. 
> > During IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized 
> > yet and so the file systems aren't accessible for JES2 to resolve. I 
> > haven't fully analyzed the system log to confirm it yet, but it seems like 
> > a reasonable assumption. Has anyone else run into this?
> 
> WAD? z/OS UNIX appears to be a second-class citizen in that operations that 
> require UNIX facilities are allowed to begin before UNIX is available, then 
> simply fail.
> 
> Should design give more attention to the order of startup operations?
> 
> Should there be an implied WAIT (not explicit) for any operation which 
> requires UNIX? Would that be likely to result in a deadlock?
> 
> --
> 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
> 
> --
> The information contained in this message is confidential, protected from 
> disclosure and may be legally privileged. If the reader of this message is 
> not the intended recipient or an employee or agent responsible for delivering 
> this message to the intended recipient, you are hereby notified that any 
> disclosure, distribution, copying, or any action taken or action omitted in 
> reliance on it, is strictly prohibited and may be unlawful. If you have 
> received this communication in error, please notify us immediately by 
> replying to this message and destroy the material in its entirety, whether in 
> electronic or hard copy format. Thank you.
> 
> --
> 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: Solarwind to z/OS

[Tom Longfellow]

My experiences with Solarwinds interacting with z/OS have not been pleasant.

First discovered it as my major source of Scanning ports of my system for 
vulnerabilities.Until I purposely put in Defensive Management Demon 
filters, they were my ONLY source of that kind of hacking attempts.  Maybe it 
was a different program on the server identifying itself as Solarwinds, but a 
bad tase is a bad taste.

Second discovery is that their software introduced  worldwide investigations 
into some questionable practices and intrusion attempts.   Defective software 
or Chinese TikTok attack V1.0.

That was enough to keep them in mind as a company to avoid. If they have 
cleaned up their game, more power to them.  If I have misread the situation, I 
apologize.  I have enough worries before trusting something with the track 
record I have experienced.

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

Re: Can REXX OUTTRAP trap WTO's?

[David Spiegel]

Hi Peter,
Assuming you  have SDSF, have you considered using its one of its APIs 
to scan the SYSLOG every n minutes?


Regards,
David

On 2023-05-09 13:55, Farley, Peter wrote:

I believe that the CONSOLE facility is authorized and I have no authorization.  
I have no access to either System Rexx or Netview Rexx.

Any other ideas?  The business need is not sufficient to request 
authorizations, this is just a script to set up some test data that would 
really be helped by capturing output generated as a WTO by an existing in-house 
utility program.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Tuesday, May 9, 2023 1:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

See the CONSOLE facility in TSO. I don't know whether it is available in System 
Rexx.


From: IBM Mainframe Discussion List  on behalf of Farley, 
Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, May 9, 2023 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Can REXX OUTTRAP trap WTO's?

Cross-posted to IBM-MAIN and TSO-REXX lists.

Is there any way for  Rexx script to capture WTO output?  This is a simple 
case, a one-line WTO, no multiline possible.

I only recently found a need to do this, and my tests so far say "no it can't".

/* Rexx */
/* Capture WTO from BATCHPGM */
xtrp = outtrap("zdsp.")
address attchmvs "BATCHPGM"
xtrp = outtrap("OFF")
say "ZDSP.1="zdsp.1

Execution result online in TSO:

*** WTO OUTPUT FROM BATCHPGM ***
ZDSP.1=ZDSP.1

Peter

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

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

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


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

Re: [EXTERNAL] Re: IBM announcement letter summary

[Pommier, Rex]

Gil,

They do at least provide the URL, I left it off for brevity.  No word as to 
whether they'll send any kind of correspondence in the future or just expect 
folks to bookmark the URL and then remember to go look on a weekly (or other 
regularly scheduled time) basis.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Tuesday, May 9, 2023 12:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IBM announcement letter summary

On Tue, 9 May 2023 16:56:56 +, Pommier, Rex wrote:
>...
>
>This weekly e-mail communication is now sunset. You can find the weekly IBM 
>product announcements on the IBM Documentation Announcements page.
>
>
Did they not supply a URL?  Shame!

>Now, instead of a short summary delivered to my inbox I have to go to IBM's 
>documentation page to find announcements.  Instead of a one-line summary per 
>announcement I now get the privilege of scrolling up and down through an 
>almost-empty web page where I can see somewhere between 6-8 notifications per 
>page.  
>
They should just put it on TikTok.

Looking at: 
, I see more than 6-8 notifications per page.  Is there a better location?  
Worse?

There is a malign WWW style rule that each page must fit on a screen, thwarting 
the "Find in Page" function.  I believe it arises from a journalistic 
convention that absurdly requires a list of 100 names to be split into 
paragraphs no longer than
8 column-cm. with a different introductory phrase for each.

--
gil

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

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


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

Re: Can REXX OUTTRAP trap WTO's?

[ITschak Mugzach]

If this process run as a batch job, the wto will be written to jesmsglg.
You may call sdsf to read your own job log...

בתאריך יום ג׳, 9 במאי 2023 ב-20:56 מאת Farley, Peter <
031df298a9da-dmarc-requ...@listserv.ua.edu>:

> I believe that the CONSOLE facility is authorized and I have no
> authorization.  I have no access to either System Rexx or Netview Rexx.
>
> Any other ideas?  The business need is not sufficient to request
> authorizations, this is just a script to set up some test data that would
> really be helped by capturing output generated as a WTO by an existing
> in-house utility program.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of Seymour J Metz
> Sent: Tuesday, May 9, 2023 1:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can REXX OUTTRAP trap WTO's?
>
> See the CONSOLE facility in TSO. I don't know whether it is available in
> System Rexx.
>
> 
> From: IBM Mainframe Discussion List  on behalf
> of Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Tuesday, May 9, 2023 1:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can REXX OUTTRAP trap WTO's?
>
> Cross-posted to IBM-MAIN and TSO-REXX lists.
>
> Is there any way for  Rexx script to capture WTO output?  This is a simple
> case, a one-line WTO, no multiline possible.
>
> I only recently found a need to do this, and my tests so far say "no it
> can't".
>
> /* Rexx */
> /* Capture WTO from BATCHPGM */
> xtrp = outtrap("zdsp.")
> address attchmvs "BATCHPGM"
> xtrp = outtrap("OFF")
> say "ZDSP.1="zdsp.1
>
> Execution result online in TSO:
>
> *** WTO OUTPUT FROM BATCHPGM ***
> ZDSP.1=ZDSP.1
>
> Peter
>
> 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
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> 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
>
-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon  *

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

Re: [EXTERNAL] Re: IBM announcement letter summary

[Pommier, Rex]

John, 

The announcement letter email wasn't just z-series.  I used to support p-series 
hardware and AIX as well, and idle curiosity has kept me getting those 
announcements as well.  They were all included in the e-mail, based on your 
preferences.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John McKown
Sent: Tuesday, May 9, 2023 12:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IBM announcement letter summary

WAG - they want to sunset the equipment that runs the functions and the z/OS 
customers are not important enough to port the process elsewhere. Or maybe they 
"released" everyone who knew anything about it.

IMO, IBM doesn't really care about that much about z anymore.

Neither do I. I'll be playing with Linux on Intel when I get kicked to the curb 
(kerb) come 1 aug 2023.

On Tue, May 9, 2023, 11:57 Pommier, Rex  wrote:

> Why, IBM?  Was sending out an announcement letter summary that taxing 
> on your limited resources that you had to eliminate this convenience 
> for your customers?
>
> Instead of the normal Tuesday announcement letter summary I got this:
>
> 
> This weekly e-mail communication is now sunset. You can find the 
> weekly IBM product announcements on the IBM Documentation Announcements page.
> 
>
> Now, instead of a short summary delivered to my inbox I have to go to 
> IBM's documentation page to find announcements.  Instead of a one-line 
> summary per announcement I now get the privilege of scrolling up and 
> down through an almost-empty web page where I can see somewhere 
> between 6-8 notifications per page.
>
> OK, rant off...
>
> Rex
>
> --
> The information contained in this message is confidential, protected 
> from disclosure and may be legally privileged. If the reader of this 
> message is not the intended recipient or an employee or agent 
> responsible for delivering this message to the intended recipient, you 
> are hereby notified that any disclosure, distribution, copying, or any 
> action taken or action omitted in reliance on it, is strictly 
> prohibited and may be unlawful. If you have received this 
> communication in error, please notify us immediately by replying to 
> this message and destroy the material in its entirety, whether in electronic 
> or hard copy format. Thank you.
>
> --
> 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

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


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

Re: Can REXX OUTTRAP trap WTO's?

[Farley, Peter]

I believe that the CONSOLE facility is authorized and I have no authorization.  
I have no access to either System Rexx or Netview Rexx.

Any other ideas?  The business need is not sufficient to request 
authorizations, this is just a script to set up some test data that would 
really be helped by capturing output generated as a WTO by an existing in-house 
utility program.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Tuesday, May 9, 2023 1:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

See the CONSOLE facility in TSO. I don't know whether it is available in System 
Rexx.


From: IBM Mainframe Discussion List  on behalf of 
Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, May 9, 2023 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Can REXX OUTTRAP trap WTO's?

Cross-posted to IBM-MAIN and TSO-REXX lists.

Is there any way for  Rexx script to capture WTO output?  This is a simple 
case, a one-line WTO, no multiline possible.

I only recently found a need to do this, and my tests so far say "no it can't".

/* Rexx */
/* Capture WTO from BATCHPGM */
xtrp = outtrap("zdsp.")
address attchmvs "BATCHPGM"
xtrp = outtrap("OFF")
say "ZDSP.1="zdsp.1

Execution result online in TSO:

*** WTO OUTPUT FROM BATCHPGM ***
ZDSP.1=ZDSP.1

Peter

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

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

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: Can REXX OUTTRAP trap WTO's?

[Farley, Peter]

The macro used is a simple assembler WTO macro with text, nothing fancy.  It is 
unfortunately not feasible to permanently change to a PUTLINE since the primary 
usage of the WTO output is in existing production batch processes, not TSO or 
Rexx usage.

I guess I could cobble up a temporary version for my immediate need though.  
Thanks for the url's.

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
ITschak Mugzach
Sent: Tuesday, May 9, 2023 1:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can REXX OUTTRAP trap WTO's?

It depends on the macro used to create the message. See below snippet from the 
manual:

However, OUTTRAP does trap output from the PUTLINE macro with DATA or INFOR 
keywords. Therefore, if you write any command processors, you may want to use 
the PUTLINE macro rather than the TPUT or WTO macros. z/OS TSO/E Programming 
Guide 
 describes how to write a TSO/E command processor. For information about the 
PUTLINE macro, see z/OS TSO/E Programming Services 
 .


בתאריך יום ג׳, 9 במאי 2023 ב-20:37 מאת Seymour J Metz :

> See the CONSOLE facility in TSO. I don't know whether it is available 
> in System Rexx.
>
> 
> From: IBM Mainframe Discussion List  on 
> behalf of Farley, Peter 
> <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Tuesday, May 9, 2023 1:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can REXX OUTTRAP trap WTO's?
>
> Cross-posted to IBM-MAIN and TSO-REXX lists.
>
> Is there any way for  Rexx script to capture WTO output?  This is a 
> simple case, a one-line WTO, no multiline possible.
>
> I only recently found a need to do this, and my tests so far say "no 
> it can't".
>
> /* Rexx */
> /* Capture WTO from BATCHPGM */
> xtrp = outtrap("zdsp.")
> address attchmvs "BATCHPGM"
> xtrp = outtrap("OFF")
> say "ZDSP.1="zdsp.1
>
> Execution result online in TSO:
>
> *** WTO OUTPUT FROM BATCHPGM ***
> ZDSP.1=ZDSP.1
>
> Peter
--

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: IBM announcement letter summary

[zMan]

I realized a couple of years ago that I'd stopped even reading the
announcements, because there was so little in there. Which is itself
symptomatic of a problem, not a rebuttal to Rex's point!

On Tue, May 9, 2023 at 1:26 PM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 9 May 2023 16:56:56 +, Pommier, Rex wrote:
> >...
> >
> >This weekly e-mail communication is now sunset. You can find the weekly
> IBM product announcements on the IBM Documentation Announcements page.
> >
> >
> Did they not supply a URL?  Shame!
>
> >Now, instead of a short summary delivered to my inbox I have to go to
> IBM's documentation page to find announcements.  Instead of a one-line
> summary per announcement I now get the privilege of scrolling up and down
> through an almost-empty web page where I can see somewhere between 6-8
> notifications per page.
> >
> They should just put it on TikTok.
>
> Looking at: <
> https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUSRA-US
> >,
> I see more than 6-8 notifications per page.  Is there a better location?
> Worse?
>
> There is a malign WWW style rule that each page must fit on a screen,
> thwarting
> the "Find in Page" function.  I believe it arises from a journalistic
> convention that
> absurdly requires a list of 100 names to be split into paragraphs no
> longer than
> 8 column-cm. with a different introductory phrase for each.
>
> --
> gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
zMan -- "I've got a mainframe and I'm not afraid to use it"

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

Re: Can REXX OUTTRAP trap WTO's?

[ITschak Mugzach]

It depends on the macro used to create the message. See below snippet from
the manual:

However, OUTTRAP does trap output from the PUTLINE macro with DATA or INFOR
keywords. Therefore, if you write any command processors, you may want to
use the PUTLINE macro rather than the TPUT or WTO macros. z/OS TSO/E
Programming Guide

describes
how to write a TSO/E command processor. For information about the PUTLINE
macro, see z/OS TSO/E Programming Services

.


בתאריך יום ג׳, 9 במאי 2023 ב-20:37 מאת Seymour J Metz :

> See the CONSOLE facility in TSO. I don't know whether it is available in
> System Rexx.
>
> 
> From: IBM Mainframe Discussion List  on behalf
> of Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Tuesday, May 9, 2023 1:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can REXX OUTTRAP trap WTO's?
>
> Cross-posted to IBM-MAIN and TSO-REXX lists.
>
> Is there any way for  Rexx script to capture WTO output?  This is a simple
> case, a one-line WTO, no multiline possible.
>
> I only recently found a need to do this, and my tests so far say "no it
> can't".
>
> /* Rexx */
> /* Capture WTO from BATCHPGM */
> xtrp = outtrap("zdsp.")
> address attchmvs "BATCHPGM"
> xtrp = outtrap("OFF")
> say "ZDSP.1="zdsp.1
>
> Execution result online in TSO:
>
> *** WTO OUTPUT FROM BATCHPGM ***
> ZDSP.1=ZDSP.1
>
> Peter
>
> 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
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon  *

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

Re: Can REXX OUTTRAP trap WTO's?

[Seymour J Metz]

See the CONSOLE facility in TSO. I don't know whether it is available in System 
Rexx.


From: IBM Mainframe Discussion List  on behalf of 
Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, May 9, 2023 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Can REXX OUTTRAP trap WTO's?

Cross-posted to IBM-MAIN and TSO-REXX lists.

Is there any way for  Rexx script to capture WTO output?  This is a simple 
case, a one-line WTO, no multiline possible.

I only recently found a need to do this, and my tests so far say "no it can't".

/* Rexx */
/* Capture WTO from BATCHPGM */
xtrp = outtrap("zdsp.")
address attchmvs "BATCHPGM"
xtrp = outtrap("OFF")
say "ZDSP.1="zdsp.1

Execution result online in TSO:

*** WTO OUTPUT FROM BATCHPGM ***
ZDSP.1=ZDSP.1

Peter

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

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

Can REXX OUTTRAP trap WTO's?

[Farley, Peter]

Cross-posted to IBM-MAIN and TSO-REXX lists.

Is there any way for  Rexx script to capture WTO output?  This is a simple 
case, a one-line WTO, no multiline possible.

I only recently found a need to do this, and my tests so far say "no it can't".

/* Rexx */
/* Capture WTO from BATCHPGM */
xtrp = outtrap("zdsp.")
address attchmvs "BATCHPGM"
xtrp = outtrap("OFF")
say "ZDSP.1="zdsp.1

Execution result online in TSO:

*** WTO OUTPUT FROM BATCHPGM ***
ZDSP.1=ZDSP.1

Peter

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: IBM announcement letter summary

[Paul Gilmartin]

On Tue, 9 May 2023 16:56:56 +, Pommier, Rex wrote:
>...
>
>This weekly e-mail communication is now sunset. You can find the weekly IBM 
>product announcements on the IBM Documentation Announcements page.
>
>
Did they not supply a URL?  Shame!

>Now, instead of a short summary delivered to my inbox I have to go to IBM's 
>documentation page to find announcements.  Instead of a one-line summary per 
>announcement I now get the privilege of scrolling up and down through an 
>almost-empty web page where I can see somewhere between 6-8 notifications per 
>page.  
>
They should just put it on TikTok.

Looking at: 
,
I see more than 6-8 notifications per page.  Is there a better location?  Worse?

There is a malign WWW style rule that each page must fit on a screen, thwarting
the "Find in Page" function.  I believe it arises from a journalistic 
convention that
absurdly requires a list of 100 names to be split into paragraphs no longer than
8 column-cm. with a different introductory phrase for each.

-- 
gil

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

Re: IBM announcement letter summary

[John McKown]

WAG - they want to sunset the equipment that runs the functions and the
z/OS customers are not important enough to port the process elsewhere. Or
maybe they "released" everyone who knew anything about it.

IMO, IBM doesn't really care about that much about z anymore.

Neither do I. I'll be playing with Linux on Intel when I get kicked to the
curb (kerb) come 1 aug 2023.

On Tue, May 9, 2023, 11:57 Pommier, Rex  wrote:

> Why, IBM?  Was sending out an announcement letter summary that taxing on
> your limited resources that you had to eliminate this convenience for your
> customers?
>
> Instead of the normal Tuesday announcement letter summary I got this:
>
> 
> This weekly e-mail communication is now sunset. You can find the weekly
> IBM product announcements on the IBM Documentation Announcements page.
> 
>
> Now, instead of a short summary delivered to my inbox I have to go to
> IBM's documentation page to find announcements.  Instead of a one-line
> summary per announcement I now get the privilege of scrolling up and down
> through an almost-empty web page where I can see somewhere between 6-8
> notifications per page.
>
> OK, rant off...
>
> Rex
>
> --
> The information contained in this message is confidential, protected from
> disclosure and may be legally privileged. If the reader of this message is
> not the intended recipient or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any disclosure, distribution, copying, or any action taken or action
> omitted in reliance on it, is strictly prohibited and may be unlawful. If
> you have received this communication in error, please notify us immediately
> by replying to this message and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
> --
> 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: HLASM

[Seymour J Metz]

If anybody with a strong z/OS HLASM background is looking for a remote 
programming position, please contact me offline. Must be able to obtain a 
public trust clearance.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IBM announcement letter summary

[Lionel B. Dyck]

+1


Lionel B. Dyck <><
Website: https://www.lbdsoftware.com
Github: https://github.com/lbdyck

“Worry more about your character than your reputation. Character is what you
are, reputation merely what others think you are.”   - - - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Pommier, Rex
Sent: Tuesday, May 9, 2023 11:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IBM announcement letter summary

Why, IBM?  Was sending out an announcement letter summary that taxing on
your limited resources that you had to eliminate this convenience for your
customers?

Instead of the normal Tuesday announcement letter summary I got this:


This weekly e-mail communication is now sunset. You can find the weekly IBM
product announcements on the IBM Documentation Announcements page.


Now, instead of a short summary delivered to my inbox I have to go to IBM's
documentation page to find announcements.  Instead of a one-line summary per
announcement I now get the privilege of scrolling up and down through an
almost-empty web page where I can see somewhere between 6-8 notifications
per page.  

OK, rant off...

Rex

--
The information contained in this message is confidential, protected from
disclosure and may be legally privileged. If the reader of this message is
not the intended recipient or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any disclosure, distribution, copying, or any action taken or action
omitted in reliance on it, is strictly prohibited and may be unlawful. If
you have received this communication in error, please notify us immediately
by replying to this message and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.

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

IBM announcement letter summary

[Pommier, Rex]

Why, IBM?  Was sending out an announcement letter summary that taxing on your 
limited resources that you had to eliminate this convenience for your customers?

Instead of the normal Tuesday announcement letter summary I got this:


This weekly e-mail communication is now sunset. You can find the weekly IBM 
product announcements on the IBM Documentation Announcements page.


Now, instead of a short summary delivered to my inbox I have to go to IBM's 
documentation page to find announcements.  Instead of a one-line summary per 
announcement I now get the privilege of scrolling up and down through an 
almost-empty web page where I can see somewhere between 6-8 notifications per 
page.  

OK, rant off...

Rex

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

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

Re: JES2 Submitlib Bootstrap problem

[Pommier, Rex]

I see a problem with this scenario.  It appears to me that there is a call (not 
necessarily by Shmuel) to potentially have JES2 wait for OMVS to be up before 
it does its startup (or at least completes the startup).  Due to a 
self-inflicted screw-up on one of our LPARs, OMVS decided it had to do a 
filesystem check on every filesystem on the system.  This took a good half hour 
where it simply appeared our LPAR was hung.  JES2 had come up and I was able to 
start a few address spaces that are dependent on JES so I could figure out what 
was going on.  Had JES been waiting for OMVS we would have been completely in 
the dark on this issue.

I could see there being communication between JES and OMVS so that when OMVS 
gets initialized it signals JES to redrive any failed zFS allocations, but 
don't force JES to wait until zFS is available.  

My $.02.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Tuesday, May 9, 2023 10:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: JES2 Submitlib Bootstrap problem

Yes, IBM absolutely should take startup sequence into account and should 
provide mechanisms to ensure that things occur in the proper order. This goes 
beyond OMVS.


--
Shmuel (Seymour J.) Metz
https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!KjMRP1Ixj6eLE0Fj!oLVba7cIWA-HvwL4aaVssbMaEZeCG3m_dnLPJgpEL8DOiFs5DAJaoVf27kYVUZyYy_Nw7UxsOVp6sogwmA$
 


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, May 9, 2023 11:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Submitlib Bootstrap problem

On Tue, 9 May 2023 12:18:11 +, Mark Jacobs wrote:

>I defined several submitlibs in my JES2PARM to use directories in a ZFS 
>filesystem. When I hotstart JES2, JES2 can find everything and is happy. 
>During IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized yet 
>and so the file systems aren't accessible for JES2 to resolve. I haven't fully 
>analyzed the system log to confirm it yet, but it seems like a reasonable 
>assumption. Has anyone else run into this?
>
WAD?  z/OS UNIX appears to be a second-class citizen in that operations that 
require UNIX facilities are allowed to begin before UNIX is available, then 
simply fail.

Should design give more attention to the order of startup operations?

Should there be an implied WAIT (not explicit) for any operation which requires 
UNIX?  Would that be likely to result in a deadlock?

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

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

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

Re: TSO IKJOPER question how about using iKJEGASI to change / get a new command buffer

[Joseph Reichman]

So the

> On May 9, 2023, at 11:14 AM, Joseph Reichman  wrote:
> 
> I could do the same with the sub command exit 
> 
>>> On May 9, 2023, at 11:10 AM, Michael Stein  wrote:
>>> 
>>> On Tue, May 09, 2023 at 07:37:27AM -0400, Joseph Reichman wrote:
>>> I am just wondering when using IKJOPER (operand) and for clarity's sake I
>>> would like to use an example from TSO TEST so I would imagine the '=' of TSO
>>> TEST is an IKJOPER
>> 
>> Well, it doesn't work like that...  Test prescans the command and
>> blanks out the '=' character..  Code from MVT IKJEGMNL:
>> 
>> SCAN EQU   *
>> *TRANSLATE AND TEST COMMAND TO DETERMINE IF IT IS AN ASSIGNMENT 
>> *COMMAND.IF NOT,LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN
>> *VERB OF COMMAND.   
>>SPACE  
>>L R4,INBUF   R4=COMMAND ADDR.  
>>LHR3,X0(,R4) NO,USE COMMAND ACTUAL LENGTH. 
>>LAR1,X4  CONSTANT OF FOUR  
>>CRR1,R3  IS THIS A NULL LINE   
>>BESCREQ1 YES --- BRANCH
>> LOOP0EQU   *
>>CLI   X4(R4),BLANK   CHECK FOR LEADING BLANK   
>>BNE   LOOP   CONTINUE. 
>>LAR4,X1(R4)  BUMP ONE. 
>>BCT   R3,LOOP0   CHECK IF ANOTHER LEADING BLANK.   
>>B SCREQ1 ALL BLANKS REQUEST NEW LINE.  
>> LOOP EQU   *
>>CLI   X4(R4),BLANK   BLANK AS A DELIMITER. 
>>BESCAN1  CAN'T BE PACH COMMAND.
>>CLI   X4(R4),LEFTPARN  LOOK FOR LEFT PAREN 
>> LEFTPARN EQU   C'('   LEFT PAREN
>>BESCAN1  THIS IS NOT A PATCH   
>>CLI   X4(R4),EQUALS  LOOK FOR EQUALS   
>> EQUALS   EQU   C'='   EQUAL SIGN
>>BESCPCH  THIS IS A PATCH   
>>LAR4,X1(R4)  ADD ONE TO ADDRESS
>>BCT   R3,LOOPFIND = OR (   
>>B SCAN1  NO FIND. CONTINUE 
>> SCPCHEQU   *  PATCH 
>>MVI   X4(R4),BLANK   BLANK OUT EQUAL SIGN FOR PARSE.   
>> BLANKEQU   C' '   BLANK.
>>L R6,PATCHSIDOBTAIN ID FOR PATCH.  
>>LHR6,X0(R6)  * 
>>B SCLINK LINK TO ASSIGNMENT COMMAND.   
>> SCAN1EQU   *
>> *LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN VERB OF COMMAND.  
>>SPACE  
>>L R4,INBUF   R4=COMMAND ADDRESS
>>L R1,WORKAREAR1=PARAMETER LIST ADDR.   
>>LAR2,N24(,R1)R2=ADDR OF FLAG WORD. 
>>LAR3,N28(,R1)R3=ADDR OF OUTPUT AREA.   
>>MVI   X0(R2),X80 INDICATE NO SYNTAX CHECK. 
>>MVC   X0(N12,R1),PARMLIST MOVE SERVICE ROUTINE PARMS   
>> * TO LIST.  
>>STM   R2,R4,N12(R1)   PLACE SCAN ROUTINE PARMS IN LIST.
>> *   
>>LINK  EP=IKJSCAN LINK TO COMMAND SCAN SERVICE ROUTINE. 
>> 
>> 
>> 
>> --
>> 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: TSO IKJOPER question

[Joseph Reichman]

I could do the same with the sub command exit 

> On May 9, 2023, at 11:10 AM, Michael Stein  wrote:
> 
> On Tue, May 09, 2023 at 07:37:27AM -0400, Joseph Reichman wrote:
>> I am just wondering when using IKJOPER (operand) and for clarity's sake I
>> would like to use an example from TSO TEST so I would imagine the '=' of TSO
>> TEST is an IKJOPER
> 
> Well, it doesn't work like that...  Test prescans the command and
> blanks out the '=' character..  Code from MVT IKJEGMNL:
> 
> SCAN EQU   *
> *TRANSLATE AND TEST COMMAND TO DETERMINE IF IT IS AN ASSIGNMENT 
> *COMMAND.IF NOT,LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN
> *VERB OF COMMAND.   
> SPACE  
> L R4,INBUF   R4=COMMAND ADDR.  
> LHR3,X0(,R4) NO,USE COMMAND ACTUAL LENGTH. 
> LAR1,X4  CONSTANT OF FOUR  
> CRR1,R3  IS THIS A NULL LINE   
> BESCREQ1 YES --- BRANCH
> LOOP0EQU   *
> CLI   X4(R4),BLANK   CHECK FOR LEADING BLANK   
> BNE   LOOP   CONTINUE. 
> LAR4,X1(R4)  BUMP ONE. 
> BCT   R3,LOOP0   CHECK IF ANOTHER LEADING BLANK.   
> B SCREQ1 ALL BLANKS REQUEST NEW LINE.  
> LOOP EQU   *
> CLI   X4(R4),BLANK   BLANK AS A DELIMITER. 
> BESCAN1  CAN'T BE PACH COMMAND.
> CLI   X4(R4),LEFTPARN  LOOK FOR LEFT PAREN 
> LEFTPARN EQU   C'('   LEFT PAREN
> BESCAN1  THIS IS NOT A PATCH   
> CLI   X4(R4),EQUALS  LOOK FOR EQUALS   
> EQUALS   EQU   C'='   EQUAL SIGN
> BESCPCH  THIS IS A PATCH   
> LAR4,X1(R4)  ADD ONE TO ADDRESS
> BCT   R3,LOOPFIND = OR (   
> B SCAN1  NO FIND. CONTINUE 
> SCPCHEQU   *  PATCH 
> MVI   X4(R4),BLANK   BLANK OUT EQUAL SIGN FOR PARSE.   
> BLANKEQU   C' '   BLANK.
> L R6,PATCHSIDOBTAIN ID FOR PATCH.  
> LHR6,X0(R6)  * 
> B SCLINK LINK TO ASSIGNMENT COMMAND.   
> SCAN1EQU   *
> *LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN VERB OF COMMAND.  
> SPACE  
> L R4,INBUF   R4=COMMAND ADDRESS
> L R1,WORKAREAR1=PARAMETER LIST ADDR.   
> LAR2,N24(,R1)R2=ADDR OF FLAG WORD. 
> LAR3,N28(,R1)R3=ADDR OF OUTPUT AREA.   
> MVI   X0(R2),X80 INDICATE NO SYNTAX CHECK. 
> MVC   X0(N12,R1),PARMLIST MOVE SERVICE ROUTINE PARMS   
> * TO LIST.  
> STM   R2,R4,N12(R1)   PLACE SCAN ROUTINE PARMS IN LIST.
> *   
> LINK  EP=IKJSCAN LINK TO COMMAND SCAN SERVICE ROUTINE. 
> 
> 
> 
> --
> 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: TSO IKJOPER question

[Michael Stein]

On Tue, May 09, 2023 at 07:37:27AM -0400, Joseph Reichman wrote:
> I am just wondering when using IKJOPER (operand) and for clarity's sake I
> would like to use an example from TSO TEST so I would imagine the '=' of TSO
> TEST is an IKJOPER

Well, it doesn't work like that...  Test prescans the command and
blanks out the '=' character..  Code from MVT IKJEGMNL:

SCAN EQU   *
*TRANSLATE AND TEST COMMAND TO DETERMINE IF IT IS AN ASSIGNMENT 
*COMMAND.IF NOT,LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN
*VERB OF COMMAND.   
 SPACE  
 L R4,INBUF   R4=COMMAND ADDR.  
 LHR3,X0(,R4) NO,USE COMMAND ACTUAL LENGTH. 
 LAR1,X4  CONSTANT OF FOUR  
 CRR1,R3  IS THIS A NULL LINE   
 BESCREQ1 YES --- BRANCH
LOOP0EQU   *
 CLI   X4(R4),BLANK   CHECK FOR LEADING BLANK   
 BNE   LOOP   CONTINUE. 
 LAR4,X1(R4)  BUMP ONE. 
 BCT   R3,LOOP0   CHECK IF ANOTHER LEADING BLANK.   
 B SCREQ1 ALL BLANKS REQUEST NEW LINE.  
LOOP EQU   *
 CLI   X4(R4),BLANK   BLANK AS A DELIMITER. 
 BESCAN1  CAN'T BE PACH COMMAND.
 CLI   X4(R4),LEFTPARN  LOOK FOR LEFT PAREN 
LEFTPARN EQU   C'('   LEFT PAREN
 BESCAN1  THIS IS NOT A PATCH   
 CLI   X4(R4),EQUALS  LOOK FOR EQUALS   
EQUALS   EQU   C'='   EQUAL SIGN
 BESCPCH  THIS IS A PATCH   
 LAR4,X1(R4)  ADD ONE TO ADDRESS
 BCT   R3,LOOPFIND = OR (   
 B SCAN1  NO FIND. CONTINUE 
SCPCHEQU   *  PATCH 
 MVI   X4(R4),BLANK   BLANK OUT EQUAL SIGN FOR PARSE.   
BLANKEQU   C' '   BLANK.
 L R6,PATCHSIDOBTAIN ID FOR PATCH.  
 LHR6,X0(R6)  * 
 B SCLINK LINK TO ASSIGNMENT COMMAND.   
SCAN1EQU   *
*LINK TO COMMAND SCAN SERVICE ROUTINE TO SCAN VERB OF COMMAND.  
 SPACE  
 L R4,INBUF   R4=COMMAND ADDRESS
 L R1,WORKAREAR1=PARAMETER LIST ADDR.   
 LAR2,N24(,R1)R2=ADDR OF FLAG WORD. 
 LAR3,N28(,R1)R3=ADDR OF OUTPUT AREA.   
 MVI   X0(R2),X80 INDICATE NO SYNTAX CHECK. 
 MVC   X0(N12,R1),PARMLIST MOVE SERVICE ROUTINE PARMS   
* TO LIST.  
 STM   R2,R4,N12(R1)   PLACE SCAN ROUTINE PARMS IN LIST.
*   
 LINK  EP=IKJSCAN LINK TO COMMAND SCAN SERVICE ROUTINE. 

 

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

Re: JES2 Submitlib Bootstrap problem

[Seymour J Metz]

Yes, IBM absolutely should take startup sequence into account and should 
provide mechanisms to ensure that things occur in the proper order. This goes 
beyond OMVS.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, May 9, 2023 11:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Submitlib Bootstrap problem

On Tue, 9 May 2023 12:18:11 +, Mark Jacobs wrote:

>I defined several submitlibs in my JES2PARM to use directories in a ZFS 
>filesystem. When I hotstart JES2, JES2 can find everything and is happy. 
>During IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized yet 
>and so the file systems aren't accessible for JES2 to resolve. I haven't fully 
>analyzed the system log to confirm it yet, but it seems like a reasonable 
>assumption. Has anyone else run into this?
>
WAD?  z/OS UNIX appears to be a second-class citizen in that operations that
require UNIX facilities are allowed to begin before UNIX is available, then
simply fail.

Should design give more attention to the order of startup operations?

Should there be an implied WAIT (not explicit) for any operation which
requires UNIX?  Would that be likely to result in a deadlock?

--
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: TSO IKJOPER question

[Joseph Reichman]

Thank you

> On May 9, 2023, at 11:02 AM, Tony Harminc  wrote:
> 
> On Tue, 9 May 2023 at 15:12, Seymour J Metz  wrote:
> 
>> I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are
>> archived (CBTTAPE?), so it should be possible to examine the source code
>> for TEST.
> 
> 
> MVS 3.8 TSO modules can also conveniently be browsed at
> http://www.mainframe.eu/mvs38/asm/TSO%20(IKJ)
> 
> The first module of the "assign" pseudo-command is IKJEGPCH. It is called
> by IKJEGMNL (the subcommand prompter), which has special code to check for
> an a=b type "command".
> 
> 
>> I would expect it to be something like
>> 
>> IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
>> OP1  IKJTERM 'Err label', ...
>> OPLIST   IKJRSVWD 'Err label'
>> IKJNAME '='
>> OP2  IKJTERM 'Err label', ...
>> 
>> The = is the operator, not a subcommand. Normally a subcommand begins with
>> a subcommand name and you use IKJSCAN to locate the offset to the
>> subcommand text; things like assignment statements are special cases.
>> 
> 
> In IKJEGPCH I see only two IKJPOSITs for the parse. But I'm not sure what
> it's working on in the command buffer, since IKJEGMNL has diddled around
> with it.
> 
> Of course this is the code as of the early 1970s, and so has doubtless
> changed quite a lot. On the other hand some of it is probably untouched.
> 
> Tony H.
> 
> --
> 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: JES2 Submitlib Bootstrap problem

[Paul Gilmartin]

On Tue, 9 May 2023 12:18:11 +, Mark Jacobs wrote:

>I defined several submitlibs in my JES2PARM to use directories in a ZFS 
>filesystem. When I hotstart JES2, JES2 can find everything and is happy. 
>During IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized yet 
>and so the file systems aren't accessible for JES2 to resolve. I haven't fully 
>analyzed the system log to confirm it yet, but it seems like a reasonable 
>assumption. Has anyone else run into this?
>
WAD?  z/OS UNIX appears to be a second-class citizen in that operations that
require UNIX facilities are allowed to begin before UNIX is available, then
simply fail.

Should design give more attention to the order of startup operations?

Should there be an implied WAIT (not explicit) for any operation which
requires UNIX?  Would that be likely to result in a deadlock?

-- 
gil

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

Re: TSO IKJOPER question

[Tony Harminc]

On Tue, 9 May 2023 at 15:12, Seymour J Metz  wrote:

> I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are
> archived (CBTTAPE?), so it should be possible to examine the source code
> for TEST.


MVS 3.8 TSO modules can also conveniently be browsed at
http://www.mainframe.eu/mvs38/asm/TSO%20(IKJ)

The first module of the "assign" pseudo-command is IKJEGPCH. It is called
by IKJEGMNL (the subcommand prompter), which has special code to check for
an a=b type "command".


> I would expect it to be something like
>
>  IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
> OP1  IKJTERM 'Err label', ...
> OPLIST   IKJRSVWD 'Err label'
>  IKJNAME '='
> OP2  IKJTERM 'Err label', ...
>
> The = is the operator, not a subcommand. Normally a subcommand begins with
> a subcommand name and you use IKJSCAN to locate the offset to the
> subcommand text; things like assignment statements are special cases.
>

In IKJEGPCH I see only two IKJPOSITs for the parse. But I'm not sure what
it's working on in the command buffer, since IKJEGMNL has diddled around
with it.

Of course this is the code as of the early 1970s, and so has doubtless
changed quite a lot. On the other hand some of it is probably untouched.

Tony H.

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

Re: TSO IKJOPER question

[Seymour J Metz]

It is not possible to use the TEST statement of IKJTSOxx to cause TEST to treat 
assignment statements as user subcommands. Furthrt, we it possible you'd need 
to duplicate the functionality of the existing assignment statement and 
distinguish a normal assignment from your version.

It is possible to process an assignment statement that you read as a 
subcommand; you just need to treat it as a special case instead of relying on 
IKJSCAN. Your code needs to recognize it as an assignment statement and pass 
the entire statement to IKJPARSE.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Joseph Reichman [reichman...@gmail.com]
Sent: Tuesday, May 9, 2023 9:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO IKJOPER question

Seymour

I can only say you are amazing

It seems it is not possible

To customize an operator like ‘=‘

As the subcommand

Must appear the first entered text

Talking in IKJTSOxx

subcmd(scmd,LOAD1)

Thank you

> On May 9, 2023, at 9:12 AM, Seymour J Metz  wrote:
>
> I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are 
> archived (CBTTAPE?), so it should be possible to examine the source code for 
> TEST. I would expect it to be something like
>
> IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
> OP1  IKJTERM 'Err label', ...
> OPLIST   IKJRSVWD 'Err label'
> IKJNAME '='
> OP2  IKJTERM 'Err label', ...
>
> The = is the operator, not a subcommand. Normally a subcommand begins with a 
> subcommand name and you use IKJSCAN to locate the offset to the subcommand 
> text; things like assignment statements are special cases.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Joseph Reichman [reichman...@gmail.com]
> Sent: Tuesday, May 9, 2023 7:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: TSO IKJOPER question
>
> Hi
>
>
>
> I am just wondering when using IKJOPER (operand) and for clarity's sake I
> would like to use an example from TSO TEST so I would imagine the '=' of TSO
> TEST is an IKJOPER
>
> Used to modify storage.
>
>
>
> The subcommand is '='
>
>
>
> Does the subcommand have to be the first operand I mean clearly in the case
> of for example 3R?=X'0001' the subcommand is the second parameter
>
>
>
> If someone could clarify this would appreciate it
>
>
>
> thanks
>
>
> --
> 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: TSO IKJOPER question

[Mike Schwab]

MVS 380 examined the source code included in the MVS 3.8 tapes that
various Hercules developers ordered from IBM.  For the most part, it
was at MVS 3.7 base level with many 3.7 PTFs, 3.8 base and PTFs not
included.  For a few products, the they attempted to update the source
code for the final MVS 3.8J binary version before enhancing a few of
the modules (IFOX assembler, etc).

On Tue, May 9, 2023 at 8:12 AM Seymour J Metz  wrote:
>
> I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are 
> archived (CBTTAPE?), so it should be possible to examine the source code for 
> TEST. I would expect it to be something like
>
>  IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
> OP1  IKJTERM 'Err label', ...
> OPLIST   IKJRSVWD 'Err label'
>  IKJNAME '='
> OP2  IKJTERM 'Err label', ...
>
> The = is the operator, not a subcommand. Normally a subcommand begins with a 
> subcommand name and you use IKJSCAN to locate the offset to the subcommand 
> text; things like assignment statements are special cases.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Joseph Reichman [reichman...@gmail.com]
> Sent: Tuesday, May 9, 2023 7:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: TSO IKJOPER question
>
> Hi
>
>
>
> I am just wondering when using IKJOPER (operand) and for clarity's sake I
> would like to use an example from TSO TEST so I would imagine the '=' of TSO
> TEST is an IKJOPER
>
> Used to modify storage.
>
>
>
> The subcommand is '='
>
>
>
> Does the subcommand have to be the first operand I mean clearly in the case
> of for example 3R?=X'0001' the subcommand is the second parameter
>
>
>
> If someone could clarify this would appreciate it
>
>
>
> thanks
>
>
> --
> 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



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: TSO IKJOPER question

[Joseph Reichman]

Seymour 

I can only say you are amazing 

It seems it is not possible 

To customize an operator like ‘=‘

As the subcommand 

Must appear the first entered text

Talking in IKJTSOxx 

subcmd(scmd,LOAD1)

Thank you 

> On May 9, 2023, at 9:12 AM, Seymour J Metz  wrote:
> 
> I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are 
> archived (CBTTAPE?), so it should be possible to examine the source code for 
> TEST. I would expect it to be something like
> 
> IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
> OP1  IKJTERM 'Err label', ...
> OPLIST   IKJRSVWD 'Err label'
> IKJNAME '='
> OP2  IKJTERM 'Err label', ...
> 
> The = is the operator, not a subcommand. Normally a subcommand begins with a 
> subcommand name and you use IKJSCAN to locate the offset to the subcommand 
> text; things like assignment statements are special cases.
> 
> 
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> 
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Joseph Reichman [reichman...@gmail.com]
> Sent: Tuesday, May 9, 2023 7:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: TSO IKJOPER question
> 
> Hi
> 
> 
> 
> I am just wondering when using IKJOPER (operand) and for clarity's sake I
> would like to use an example from TSO TEST so I would imagine the '=' of TSO
> TEST is an IKJOPER
> 
> Used to modify storage.
> 
> 
> 
> The subcommand is '='
> 
> 
> 
> Does the subcommand have to be the first operand I mean clearly in the case
> of for example 3R?=X'0001' the subcommand is the second parameter
> 
> 
> 
> If someone could clarify this would appreciate it
> 
> 
> 
> thanks
> 
> 
> --
> 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: TSO IKJOPER question

[Seymour J Metz]

I believe that the optional source tapes for OS/360 and OS/VS2 3.8 are archived 
(CBTTAPE?), so it should be possible to examine the source code for TEST. I 
would expect it to be something like

 IKJOPER 'Err label',OPERND1=OP1,RSVWD=OPLIST,OPERND2=OP2
OP1  IKJTERM 'Err label', ...
OPLIST   IKJRSVWD 'Err label'
 IKJNAME '='
OP2  IKJTERM 'Err label', ...

The = is the operator, not a subcommand. Normally a subcommand begins with a 
subcommand name and you use IKJSCAN to locate the offset to the subcommand 
text; things like assignment statements are special cases.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Joseph Reichman [reichman...@gmail.com]
Sent: Tuesday, May 9, 2023 7:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO IKJOPER question

Hi



I am just wondering when using IKJOPER (operand) and for clarity's sake I
would like to use an example from TSO TEST so I would imagine the '=' of TSO
TEST is an IKJOPER

Used to modify storage.



The subcommand is '='



Does the subcommand have to be the first operand I mean clearly in the case
of for example 3R?=X'0001' the subcommand is the second parameter



If someone could clarify this would appreciate it



thanks


--
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: XLC version? [was: RE: XLC - Weak symbols]

[Steve Smith]

Yeah, I've been just as confused as anyone.  It doesn't make much sense to
have an entirely new compiler ("Open XL C/C++") with a name so subtly
different from the old one ("XL C/C++").  It's typical of IBM to add &
remove fashionable buzzwords to/from product names with no significance.
So this is definitely causing a lot of confusion.

And if the salient feature of XL C/C++ 3.4.1 is that it drops support for
running on MVS, then that's just nuts.  It would seem to imply there is
*no* future for MVS C/C++, and it sure seems like a major change that
deserves more than a minor mod-level update.

And maybe I'm still confused.

sas


On Tue, May 9, 2023 at 12:29 AM Phil Smith III  wrote:

> David Crayford wrote:
>
> >They're different products. I can't see a convergence as that would be
>
> >a high impact change to customers and would require Metal/C spinning
>
> >off. It's far more likely that XL 2.4.1 and Open XL C/C++ will
>
> >converge.
>
>
>
> Huh, something gave me the impression that 2.4.1 was Open XL C/C++. The
> fact that it looks like a slight update to 2.4 of XL C is, of course, a big
> part of the problem here!
>
>
>
> I would very much like to understand what's what and what's going where
> here, for planning purposes. IBM? Please?
>
>
> --
> 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: Logical Nor (¬) in ASCII-based code pages?

[David Spiegel]

Hi Phil,
Tsuris?! ... Maybe farklempt is more apt?
(For people of Yeshivish background (like me) Ogmas Nefesh is even closer.)

Regards,
David

On 2023-05-09 00:26, Phil Smith III wrote:

Seymour,

  


Since you seem to be getting upset about this academic discussion, I will bow 
out. No need for tsuris over 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: Logical Nor (¬) in ASCII-based code pages?

[Seymour J Metz]

No, I'm getting upset about trying to put words in my mouth; that's not 
something that is acceptable in Academia.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Phil Smith III [li...@akphs.com]
Sent: Tuesday, May 9, 2023 12:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logical Nor (¬) in ASCII-based code pages?

Seymour,



Since you seem to be getting upset about this academic discussion, I will bow 
out. No need for tsuris over 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

JES2 Submitlib Bootstrap problem

[Mark Jacobs]

I defined several submitlibs in my JES2PARM to use directories in a ZFS 
filesystem. When I hotstart JES2, JES2 can find everything and is happy. During 
IPL/JES2 startup it's not. It doesn't seem like OMVS is initialized yet and so 
the file systems aren't accessible for JES2 to resolve. I haven't fully 
analyzed the system log to confirm it yet, but it seems like a reasonable 
assumption. Has anyone else run into this?

Mark Jacobs

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com

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

TSO IKJOPER question

[Joseph Reichman]

Hi

 

I am just wondering when using IKJOPER (operand) and for clarity's sake I
would like to use an example from TSO TEST so I would imagine the '=' of TSO
TEST is an IKJOPER

Used to modify storage. 

 

The subcommand is '='

 

Does the subcommand have to be the first operand I mean clearly in the case
of for example 3R?=X'0001' the subcommand is the second parameter 

 

If someone could clarify this would appreciate it

 

thanks


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