Re: Real fun for companies on older machines & SCRT

[Timothy Sipples]

John McKown wrote:
>1.12

That's very likely your actual problem. The IBM SDK for z/OS, Java Technology 
Edition, Version 8 definitely requires z/OS 1.13 or higher.

>Java 8 won't run on our z9 due to ALS level.

That's incorrect. Even the z890/z990 model generation can run Java 8, and your 
machine is one model generation newer than that.

If you have a "sandbox" LPAR with z/OS 1.13 or z/OS 2.1 you can try again. 
(z/OS 1.13 and 2.1 are the only two z/OS releases that are compatible with both 
IBM z9 BC machines and Java 8.)

— — — — —
Timothy Sipples
Senior Architect
Digital Assets, Industry Solutions, and Cybersecurity
IBM zSystems/LinuxONE, Asia-Pacific
sipp...@sg.ibm.com


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

Re: bpxpqrmxx and $SYSNAME vs

[Lizette Koehler]

Thank you everyone  This is what I thought.



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Steve Smith
Sent: Monday, September 12, 2022 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: bpxpqrmxx and $SYSNAME vs 

The examples from the FM seem to generally use &-symbols when available, and 
$-symbols when not.  $VERSION for example isn't a system-provided symbol, 
although I assign it from 

On a rather tangential rant, I am annoyed with people who gratuitously stuff 
$$$ all over in volsers, dsnames, and anything else they get their hands on, 
evidently just because they think $$$ are so sexy.  Inside USS, these become 
extremely annoying in trying to figure out the required escapage.

sas


On Mon, Sep 12, 2022 at 11:15 AM Carmen Vitullo  wrote:

> I know the $SYSNAME. resolves to the system name but in my BPXPRMxx 
> member I use //etc and //var
>
> I use /$VERSION for my mount-point for the SYSRES specific mount point 
> for the version ROOT
>
> Carmen
>
>

--
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: Ad 33rd Rexx Language Symposium coming up next week (September 12th - September 14th 2022)

[Hobart Spitz]

Dr. Rony;

I hope this reaches you in time for a response.

According to my reading of the Symposium schedule, registration should be
starting now.  I don't see an active link for even the "General Meeting."
If I've mis-read or there was a technical issue, please let me know how to
adjust my plans for CDT, Dallas.  As of this writing it is 18:33.

Thanks.

All the best.

- Hobart Spitz
(USA, cell) 443-297-7879



OREXXMan
Q: What do you call the residence of the ungulate with the largest antlers?
A: A moose pad.
:-D
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)?  Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.


On Wed, Sep 7, 2022 at 4:48 AM Rony G. Flatscher 
wrote:

> This year's International Rexx Language symposium takes place digitally
> (via Zoom) next week from
> Monday, September 12th, to Wednesday, September 14th.
>
> This year the presentations are scheduled to fit the US American time-zone
> the best. Here the
> easiest way to get there: go to  then click the
> button entitled "2022
> Schedule" on the upper right hand corner.
>
> Note: the presentation schedule times are given in the timezone your
> browser reports, so they are
> displayed in your own local time-zone.
>
> One remark ad those who work in Java here and wish to be able to implement
> Rexx command handlers in
> Java (or NetRexx for that matter): there are two presentations that
> explain and showcase how to
> implement Rexx exit handler and Rexx command handlers in Java. You will
> see that it is fairly
> straight-forward to implement Rexx handlers in Java, allowing one to add
> new command handlers (but
> also replace existing command handlers by new implementations).
>
> And the symposium is *the* opportunity to ask questions in person to all
> the presenters e.g. to Mark
> Hessling (Regina) and anyone else there.
>
> ---rony
>
>
>
>
>
> --
> --
>
> __
>
> Prof. Dr. Rony G. Flatscher
> Department Wirtschaftsinformatik und Operations Management
> Institut für Wirtschaftsinformatik und Gesellschaft
> D2c 2.086
> WU Wien
> Welthandelsplatz 1
> A-1020  Wien/Vienna, Austria/Europe
>
> http://www.wu.ac.at
>
> __
>
> --
> 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: Why is my second Rexx SYSCALLS read failing?

[Paul Gilmartin]

Thanks for trimming to relevant sentences, excluding LISTSERV footers;
a rare courtesy hereabouts.

On Mon, 12 Sep 2022 17:08:19 -0500, Charles Mills wrote:
>
>Ah! A case of RTFM.
>
Rather, scrutinize minutely and memorize TFM.  You just happened to touch on
a construct I had used.

>One tends to get started using a tool without later going back and educating 
>oneself from the top down.
>
A more complete excerpt from 
:
Informal Introduction to ALGOL 68
C. H. Lindsey, S. G. van Der Meulen

0.0. Aims and methods
Since ALGOL 68 is a highly recursively structured language, it is quite 
impossible to describe it until it has been described. So that you can read 
this Introduction without tying your own mental processes into a recursive 
knot, it has been laid out to a certain pattern, which we ask you to follow. 
Please, therefore, start by reading once or twice "Very Informal Introduction", 
in
which we try to give a broad survey of what is in this language - mainly by the 
way of small examples and plain explanations. Aft~r that, we shall tell you 
what to do next.
if you think you know it all already .
then
read (what to do next) comment Section 0.14 comment
fi

-- 
gil

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

Re: Why is my second Rexx SYSCALLS read failing?

[Charles Mills]

> Ah!  A coding error.

Yep! Pretty much knew it was either a coding error or an "understanding error." 
I am about fifty years past the point of starting out with "I think I found a 
bug in the compiler." (Yes, it does happen.)

> A variable name enclosed in parentheses

Ah! A case of RTFM.

One tends to get started using a tool without later going back and educating 
oneself from the top down.

Thanks again,
Charles

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

Re: Ad 33rd Rexx Language Symposium coming up next week (September 12th - September 14th 2022)

[René Jansen]

If you are logged on, and go to the symposium schedule for 2022, you should see 
it. It also was sent out to the rexxla-memb...@groups.io 
 list.

best regards,

René.


> On 12 Sep 2022, at 22:38, Seymour J Metz  wrote:
> 
> I joined but I didn't receive a symposium link.
> 
> 
> From: IBM Mainframe Discussion List  > on behalf of René Jansen 
> mailto:rene.vincent.jan...@gmail.com>>
> Sent: Wednesday, September 7, 2022 10:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: Ad 33rd Rexx Language Symposium coming up next week (September 
> 12th - September 14th 2022)
> 
> There is no registration required. RexxLA is free, but donations are accepted 
> and appreciated. Daily links to the Zoom will be posted on the RexxLA mailing 
> list and website.
> 
> Questions can be asked in advance, address presid...@rexxla.org 
>   > - there will be a Q session with Mike 
> Cowlishaw that is not on the schedule yet.
> 
> Best regards,
> 
> René.
> 
>> On 7 Sep 2022, at 16:39, Seymour J Metz  wrote:
>> 
>> Where is the registration link? Can questions be posted in advance? Thanks.
>> 
>> 
>> --
>> Shmuel (Seymour J.) Metz
>> http://mason.gmu.edu/~smetz3
>> 
>> 
>> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
>> Rony G. Flatscher [rony.flatsc...@wu.ac.at]
>> Sent: Wednesday, September 7, 2022 5:47 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Ad 33rd Rexx Language Symposium coming up next week (September 12th 
>> - September 14th 2022)
>> 
>> This year's International Rexx Language symposium takes place digitally (via 
>> Zoom) next week from
>> Monday, September 12th, to Wednesday, September 14th.
>> 
>> This year the presentations are scheduled to fit the US American time-zone 
>> the best. Here the
>> easiest way to get there: go to 
>> 
>>  then click the button entitled "2022
>> Schedule" on the upper right hand corner.
>> 
>> Note: the presentation schedule times are given in the timezone your browser 
>> reports, so they are
>> displayed in your own local time-zone.
>> 
>> One remark ad those who work in Java here and wish to be able to implement 
>> Rexx command handlers in
>> Java (or NetRexx for that matter): there are two presentations that explain 
>> and showcase how to
>> implement Rexx exit handler and Rexx command handlers in Java. You will see 
>> that it is fairly
>> straight-forward to implement Rexx handlers in Java, allowing one to add new 
>> command handlers (but
>> also replace existing command handlers by new implementations).
>> 
>> And the symposium is *the* opportunity to ask questions in person to all the 
>> presenters e.g. to Mark
>> Hessling (Regina) and anyone else there.
>> 
>> ---rony
>> 
>> 
>> 
>> 
>> 
>> --
>> --
>> __
>> 
>> Prof. Dr. Rony G. Flatscher
>> Department Wirtschaftsinformatik und Operations Management
>> Institut für Wirtschaftsinformatik und Gesellschaft
>> D2c 2.086
>> WU Wien
>> Welthandelsplatz 1
>> A-1020  Wien/Vienna, Austria/Europe
>> 
>> http://secure-web.cisco.com/1vpahZIjBcNO4WDx3s7YPJcXWDE6tnjCxgQrxapK4mU2sCXAbebVIub-rWAlkoT7g_voVZHcvYWNDELFeb0a035_6KFn251HeyCvCpGWVNtCvTUuZaSx__qcd0kKkDfze5yc_yxrhhTQBz3L_uV-F30DPVvc6MaxoqsWkB8xlCL1p49wlBM6FZsEGE5UTJP2zk99N_u_GQsOul_9aABzPGpHNA1a51fTS1xPYJo1VsUqcbfOtmn9xdRcFJ4xwsU9IBC_IzZtJ-yLdT7D0q-Q6FkAKhRrSrPTQuaJDce_RA5MotcEfTSRlFfhQg7RLrsPKDIX2kI-HnoLH42smT2htANJCFtXhp6q06PsJf6W75jj5fWYDoGDF42PhqBmgG7len_VYljzq94P6diaFQipn7L4oJkz4OOzeqC_qJsjoDxG1p2rqEypEGkYfBrYgOfVk5GL2RPbOQfBCVQwE5UHxIA/http%3A%2F%2Fwww.wu.ac.at
>> __
>> 
>> --
>> 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 

Re: How to use LISTDSI from Rexx under Unix shell?

[Farley, Peter x23353]

Apologies, I spotted a typo after hitting send:

3.  The TESTLSA, TESTREXA1, and TESTREXA3 scripts are duplicates of the 
TESTLS, TESTREX1, and TESTREX3 scripts but stored as ISO8859 text rather than 
as IBM1047 text.

TESTREX3, not TESTREX2

Peter

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Farley, Peter x23353
Sent: Monday, September 12, 2022 3:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to use LISTDSI from Rexx under Unix shell?

EXTERNAL EMAIL

I finally found the round tuits to finish this exercise, so here is what I 
found works.  I hope my test pastes here make it through the listserver 
manipulations.  Apologies if they do not.

Setup:

1.  In my Unix $HOME directory I created a new "exec" directory
2.  Below are listed the contents of that "exec" directory with CCSID tags 
shown (and non-relevant lines omitted), followed by a listing of each of the 
three scripts TESTLS, TESTREX1, TESTREX3
3.  The TESTLSA, TESTREXA1, and TESTREXA3 scripts are duplicates of the 
TESTLS, TESTREX1, and TESTREX2 scripts but stored as ISO8859 text rather than 
as IBM1047 text.
4.  The PDSE named TSOUSER.EXEC contains a copy of TESTLS identical to the 
/u/tsouser/exec/TESTLS file

The TESTREX1 script executes the TESTLS script stored in the TSOUSER.EXEC PDSE. 
 The TESTREX3 script executes the TESTLS script stored in 
/u/tsouser/exec/TESTLS.

The TESTLS script executes a LISTDSI using the DSN passed as its only argument 
and prints out the RC and SYSREASON from the LISTDSI, and if the RC is zero it 
then prints some of the LISTDSI returned variable contents.

Listed first below are the results of running the TESTREX1 and TESTREX3 scripts 
directly from the Unix shell command prompt.  Note that running the ISO8859 
versions TESTREXA1 or TESTREXA3 will generate the same results as TESTREX1 and 
TESTREX3.  The key requirement is that if you want to execute a Rexx script 
stored in a Unix directory under "ADDRESS TSO" then that script MUST be coded 
in IBM1047 (or, I suspect, any valid EBCDIC CCSID).  The "starting" script (the 
one you execute from the shell prompt) can be coded in either an EBCDIC CCSID 
or in ISO8859 (and probably also UTF-8) but that capability is probably under 
the influence of the AUTOCVT option(s).

The first key takeaway is that a Rexx script stored in the Unix file system and 
executed under "ADDRESS TSO" in a Rexx script executed from the shell MUST be 
stored in an EBCDIC CCSID.  If you change the Unix-stored script name to be 
executed under "ADDRESS TSO" in the TESTREX3 script to TESTLSA (the ISO8859 
version), it fails with a WRNG.LEN.REC I/O error from BPAM.

The second key takeaway is that the stack does not survive the transition from 
"ADDRESS TSO" back to the script executing under the shell.  I tried using 
"QUEUE" instead of "SAY" in the TESTLS script, but the values stacked got 
"executed" under the "ADDRESS TSO" umbrella, so "ADDRESS TSO" scripts that want 
to return data have to use "SAY" to transmit information back to the invoking 
script.

Peter

/u/tsouser/exec > TESTREX1 'TSOUSER.EXEC'
 3 *-* parse source env how fullname fromddn fromdsn fromname hostcmd 
hostasn
   >>>   "TSO"
   >>>   "COMMAND"
   >>>   "./exec/TESTREX1"
   >>>   "PATH"
   >>>   "./exec/TESTREX1"
   >>>   "?"
   >>>   "SH"
   >>>   "OMVS OpenMVS"
 4 *-* SAY "PARSE SOURCE =" env how fullname fromddn fromdsn fromname 
hostcmd hostasn
   >>>   "PARSE SOURCE = TSO COMMAND ./exec/TESTREX1 PATH ./exec/TESTREX1 ? 
SH OMVS OpenMVS"
PARSE SOURCE = TSO COMMAND ./exec/TESTREX1 PATH ./exec/TESTREX1 ? SH OMVS 
OpenMVS
 5 *-* CALL OUTTRAP OUT.
   >>>   "OUT."
   >>>   "OUT."
 6 *-* ADDRESS TSO
 7 *-* "ALLOC FI(SYSEXEC) DA('TSOUSER.EXEC') SHR"
   >>>   "ALLOC FI(SYSEXEC) DA('TSOUSER.EXEC') SHR"
 8 *-* "TESTLS 'TSOUSER.EXEC'"
   >>>   "TESTLS 'TSOUSER.EXEC'"
 9 *-* "FREE FI(SYSEXEC)"
   >>>   "FREE FI(SYSEXEC)"
10 *-* DO I=1 TO OUT.0
   >>>   "1"
   >>>   "4"
11 *-*  SAY OUT.I
   >>>"PARSE SOURCE = TSO COMMAND TESTLS SYSEXEC ? ? TSO TSO/E ?"
PARSE SOURCE = TSO COMMAND TESTLS SYSEXEC ? ? TSO TSO/E ?
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"RUNNING LISTDSI('TSOUSER.EXEC')"
RUNNING LISTDSI('TSOUSER.EXEC')
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"LISTDSI RC = 0 REASON = "
LISTDSI RC = 0 REASON = 
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"DSN=TSOUSER.EXEC,DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=32720"
DSN=TSOUSER.EXEC,DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=32720
12 *-* END
10 *-* DO I=1 TO OUT.0
13 *-* EXIT

/u/tsouser/exec > TESTREX3 'TSOUSER.EXEC'
 3 *-* parse source env how fullname fromddn fromdsn fromname hostcmd 
hostasn
   >>>   "TSO"
   >>>   "COMMAND"
   >>>   "./exec/TESTREX3"
   >>>   "PATH"
   >>>   

Re: z/VSE Support Education and Manuals

[Mike Schwab]

https://www.ibm.com/docs/en/zvse/6.2?topic=SSB27H_6.2.0/zvse_welcome_6.2.0.html

If you want a practice system, Hercules has 5 downloads.  DOS has had
minimal updates beyond what was needed to run on newer hardware.
https://hercules-390.github.io/html/

On Mon, Sep 12, 2022 at 1:09 PM Jasi Grewal
<040674ae00fc-dmarc-requ...@listserv.ua.edu> wrote:
>
> Hi, I have been requested to support z/VSE Platform, since I support z/VM and 
> z/OS Systems.Since,  I have not used VSE systems for 40Yrs, I would be 
> interested in learning any information which would help me support z/VSE 
> Environments.
> If you have any information which would help me then I would be really 
> grateful.
> Thank You in advance,Regards,Jasi Grewal.
>
> --
> 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: Ad 33rd Rexx Language Symposium coming up next week (September 12th - September 14th 2022)

[Seymour J Metz]

I joined but I didn't receive a symposium link.


From: IBM Mainframe Discussion List  on behalf of 
René Jansen 
Sent: Wednesday, September 7, 2022 10:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Ad 33rd Rexx Language Symposium coming up next week (September 
12th - September 14th 2022)

There is no registration required. RexxLA is free, but donations are accepted 
and appreciated. Daily links to the Zoom will be posted on the RexxLA mailing 
list and website.

Questions can be asked in advance, address presid...@rexxla.org 
 - there will be a Q session with Mike Cowlishaw 
that is not on the schedule yet.

Best regards,

René.

> On 7 Sep 2022, at 16:39, Seymour J Metz  wrote:
>
> Where is the registration link? Can questions be posted in advance? Thanks.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Rony G. Flatscher [rony.flatsc...@wu.ac.at]
> Sent: Wednesday, September 7, 2022 5:47 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Ad 33rd Rexx Language Symposium coming up next week (September 12th 
> - September 14th 2022)
>
> This year's International Rexx Language symposium takes place digitally (via 
> Zoom) next week from
> Monday, September 12th, to Wednesday, September 14th.
>
> This year the presentations are scheduled to fit the US American time-zone 
> the best. Here the
> easiest way to get there: go to 
> 
>  then click the button entitled "2022
> Schedule" on the upper right hand corner.
>
> Note: the presentation schedule times are given in the timezone your browser 
> reports, so they are
> displayed in your own local time-zone.
>
> One remark ad those who work in Java here and wish to be able to implement 
> Rexx command handlers in
> Java (or NetRexx for that matter): there are two presentations that explain 
> and showcase how to
> implement Rexx exit handler and Rexx command handlers in Java. You will see 
> that it is fairly
> straight-forward to implement Rexx handlers in Java, allowing one to add new 
> command handlers (but
> also replace existing command handlers by new implementations).
>
> And the symposium is *the* opportunity to ask questions in person to all the 
> presenters e.g. to Mark
> Hessling (Regina) and anyone else there.
>
> ---rony
>
>
>
>
>
> --
> --
> __
>
> Prof. Dr. Rony G. Flatscher
> Department Wirtschaftsinformatik und Operations Management
> Institut für Wirtschaftsinformatik und Gesellschaft
> D2c 2.086
> WU Wien
> Welthandelsplatz 1
> A-1020  Wien/Vienna, Austria/Europe
>
> http://secure-web.cisco.com/1vpahZIjBcNO4WDx3s7YPJcXWDE6tnjCxgQrxapK4mU2sCXAbebVIub-rWAlkoT7g_voVZHcvYWNDELFeb0a035_6KFn251HeyCvCpGWVNtCvTUuZaSx__qcd0kKkDfze5yc_yxrhhTQBz3L_uV-F30DPVvc6MaxoqsWkB8xlCL1p49wlBM6FZsEGE5UTJP2zk99N_u_GQsOul_9aABzPGpHNA1a51fTS1xPYJo1VsUqcbfOtmn9xdRcFJ4xwsU9IBC_IzZtJ-yLdT7D0q-Q6FkAKhRrSrPTQuaJDce_RA5MotcEfTSRlFfhQg7RLrsPKDIX2kI-HnoLH42smT2htANJCFtXhp6q06PsJf6W75jj5fWYDoGDF42PhqBmgG7len_VYljzq94P6diaFQipn7L4oJkz4OOzeqC_qJsjoDxG1p2rqEypEGkYfBrYgOfVk5GL2RPbOQfBCVQwE5UHxIA/http%3A%2F%2Fwww.wu.ac.at
> __
>
> --
> 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: How to use LISTDSI from Rexx under Unix shell?

[Farley, Peter x23353]

I finally found the round tuits to finish this exercise, so here is what I 
found works.  I hope my test pastes here make it through the listserver 
manipulations.  Apologies if they do not.

Setup:

1.  In my Unix $HOME directory I created a new "exec" directory
2.  Below are listed the contents of that "exec" directory with CCSID tags 
shown (and non-relevant lines omitted), followed by a listing of each of the 
three scripts TESTLS, TESTREX1, TESTREX3
3.  The TESTLSA, TESTREXA1, and TESTREXA3 scripts are duplicates of the 
TESTLS, TESTREX1, and TESTREX2 scripts but stored as ISO8859 text rather than 
as IBM1047 text.
4.  The PDSE named TSOUSER.EXEC contains a copy of TESTLS identical to the 
/u/tsouser/exec/TESTLS file

The TESTREX1 script executes the TESTLS script stored in the TSOUSER.EXEC PDSE. 
 The TESTREX3 script executes the TESTLS script stored in 
/u/tsouser/exec/TESTLS.

The TESTLS script executes a LISTDSI using the DSN passed as its only argument 
and prints out the RC and SYSREASON from the LISTDSI, and if the RC is zero it 
then prints some of the LISTDSI returned variable contents.

Listed first below are the results of running the TESTREX1 and TESTREX3 scripts 
directly from the Unix shell command prompt.  Note that running the ISO8859 
versions TESTREXA1 or TESTREXA3 will generate the same results as TESTREX1 and 
TESTREX3.  The key requirement is that if you want to execute a Rexx script 
stored in a Unix directory under "ADDRESS TSO" then that script MUST be coded 
in IBM1047 (or, I suspect, any valid EBCDIC CCSID).  The "starting" script (the 
one you execute from the shell prompt) can be coded in either an EBCDIC CCSID 
or in ISO8859 (and probably also UTF-8) but that capability is probably under 
the influence of the AUTOCVT option(s).

The first key takeaway is that a Rexx script stored in the Unix file system and 
executed under "ADDRESS TSO" in a Rexx script executed from the shell MUST be 
stored in an EBCDIC CCSID.  If you change the Unix-stored script name to be 
executed under "ADDRESS TSO" in the TESTREX3 script to TESTLSA (the ISO8859 
version), it fails with a WRNG.LEN.REC I/O error from BPAM.

The second key takeaway is that the stack does not survive the transition from 
"ADDRESS TSO" back to the script executing under the shell.  I tried using 
"QUEUE" instead of "SAY" in the TESTLS script, but the values stacked got 
"executed" under the "ADDRESS TSO" umbrella, so "ADDRESS TSO" scripts that want 
to return data have to use "SAY" to transmit information back to the invoking 
script.

Peter

/u/tsouser/exec > TESTREX1 'TSOUSER.EXEC'
 3 *-* parse source env how fullname fromddn fromdsn fromname hostcmd 
hostasn
   >>>   "TSO"
   >>>   "COMMAND"
   >>>   "./exec/TESTREX1"
   >>>   "PATH"
   >>>   "./exec/TESTREX1"
   >>>   "?"
   >>>   "SH"
   >>>   "OMVS OpenMVS"
 4 *-* SAY "PARSE SOURCE =" env how fullname fromddn fromdsn fromname 
hostcmd hostasn
   >>>   "PARSE SOURCE = TSO COMMAND ./exec/TESTREX1 PATH ./exec/TESTREX1 ? 
SH OMVS OpenMVS"
PARSE SOURCE = TSO COMMAND ./exec/TESTREX1 PATH ./exec/TESTREX1 ? SH OMVS 
OpenMVS
 5 *-* CALL OUTTRAP OUT.
   >>>   "OUT."
   >>>   "OUT."
 6 *-* ADDRESS TSO
 7 *-* "ALLOC FI(SYSEXEC) DA('TSOUSER.EXEC') SHR"
   >>>   "ALLOC FI(SYSEXEC) DA('TSOUSER.EXEC') SHR"
 8 *-* "TESTLS 'TSOUSER.EXEC'"
   >>>   "TESTLS 'TSOUSER.EXEC'"
 9 *-* "FREE FI(SYSEXEC)"
   >>>   "FREE FI(SYSEXEC)"
10 *-* DO I=1 TO OUT.0
   >>>   "1"
   >>>   "4"
11 *-*  SAY OUT.I
   >>>"PARSE SOURCE = TSO COMMAND TESTLS SYSEXEC ? ? TSO TSO/E ?"
PARSE SOURCE = TSO COMMAND TESTLS SYSEXEC ? ? TSO TSO/E ?
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"RUNNING LISTDSI('TSOUSER.EXEC')"
RUNNING LISTDSI('TSOUSER.EXEC')
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"LISTDSI RC = 0 REASON = "
LISTDSI RC = 0 REASON = 
12 *-* END
10 *-* DO I=1 TO OUT.0
11 *-*  SAY OUT.I
   >>>"DSN=TSOUSER.EXEC,DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=32720"
DSN=TSOUSER.EXEC,DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=32720
12 *-* END
10 *-* DO I=1 TO OUT.0
13 *-* EXIT

/u/tsouser/exec > TESTREX3 'TSOUSER.EXEC'
 3 *-* parse source env how fullname fromddn fromdsn fromname hostcmd 
hostasn
   >>>   "TSO"
   >>>   "COMMAND"
   >>>   "./exec/TESTREX3"
   >>>   "PATH"
   >>>   "./exec/TESTREX3"
   >>>   "?"
   >>>   "SH"
   >>>   "OMVS OpenMVS"
 4 *-* SAY "PARSE SOURCE =" env how fullname fromddn fromdsn fromname 
hostcmd hostasn
   >>>   "PARSE SOURCE = TSO COMMAND ./exec/TESTREX3 PATH ./exec/TESTREX3 ? 
SH OMVS OpenMVS"
PARSE SOURCE = TSO COMMAND ./exec/TESTREX3 PATH ./exec/TESTREX3 ? SH OMVS 
OpenMVS
 5 *-* CALL OUTTRAP OUT.
   >>>   "OUT."
   >>>   "OUT."
 6 *-* ADDRESS TSO
 7 *-* "ALLOC FI(SYSEXEC) PATH('/u/tsouser/exec') 

Re: refresh system symbols

[Colin Paice]

Peter,

I was going to suggest

*The SETLOAD

command can be used to refresh system symbols via a LOADxx member.*

   - *If you have the LOADxx members in the PARMLIB concatenation, (and so
   are not using SYS1.IPLPARM) the SETLOAD WS,IEASYM, command will refresh the
   symbols.*
   - *If you have the LOADxx members in SYS1.IPLPARM, then you need to use
   the command like SETLOAD xx,IEASYM,DSN=SYS1.IPLPARM or setload
   xx,IEASYM,DSN=SYS1.IPLPARM,VOL=A5SYS1, giving the name, and optionally the
   volume of the dataset containing the LOADxx member.*

*Typically you will use the same LOADxx member as used at IPL.  You can use
a different LOADxx to that used at IPL - so you can change your symbols
after the IPL has finished.*

*Note: The entire set of symbols are deleted, and the specified symbols
added, so you need to reload all of them. For example if you specified
IEASYM (xx,yy) at IPL, and used SETLOAD with just IEASYMyy, you will lose
the symbols from IEASYMxx*.

I fell over the problem of just refreshing IEASYSyy instead of using IEASYM
(xx,yy) and had lots of problems ( grin)

Colin




On Sun, 11 Sept 2022 at 13:46, Peter Relson  wrote:

> Michael Babcock's comment was fully correct and on point.
>
> If you have LOADxx in SYS1.IPLPARM on volume VOL123 and that dataset is
> not in the parmlib concatenation then
> SETLOAD xx,IEASYM,DSN=SYS1.IPLPARM,VOL=VOL123
> applies.
>
> And, as is described, you can use
> SETLOAD xx,IEASYM,DSN=IPL,VOL=IPL
> To indicate to take the dataset and volume used from IPL to locate LOADxx.
>
> Colin, what commentary update are you thinking of requesting?
> The doc indicates that the default is to locate LOADxx via the parmlib
> concatenation (which is true) and shows how to override the default.
> There's almost always room for improvement in documentation
>
> 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
>

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

Re: Why is my second Rexx SYSCALLS read failing?

[Paul Gilmartin]

On Mon, 12 Sep 2022 11:49:07 -0500, Charles Mills wrote:
>...
>The file names are constructed by the program. Each file covers one month. The 
>user specifies a date range and the program constructs the appropriate file 
>names. It was getting the first one right but subsequent ones wrong. 
> 
Ah!  A coding error.

>...
>The file names are constructed by the program and should never be perverse. 
>They are not user input.
> 
Provided that you make no coding errors.  Programmer's taste whether
-21 from SYSCALL or ENOENT from open is more lucid.

>I find the documentation very lacking in "big picture." 
>
There's a facetious statement in the intro to the ALGOL-68 reference (roughly,
from memory): "Since the syntax of ALGOL-68 is specified recursively, it is
impossible to explain it until it has been explained ..."  This applies to many
languages.  Consider DFSORT.

>... The examples are often nearly useless. Is that (FN) syntax documented 
> anywhere? I take it that the parentheses dereference FN so that the filename 
> is the value of FN, not "FN" literally. Is that documented anywhere? Is there 
> a SHARE presentation or anything like that that gives a big picture and some 
> seriously useful examples?
> 
It's easy to find the answer when you already know it.  I'll call this "Brin's 
Law".
Many years ago, I asked the converse question on MVS-OE and WJS generously 
replied.


...
A variable name enclosed in parentheses. Strings that contain both the single
quotation mark and double quotation mark characters must be stored in a
variable, and you must use the variable name.

-- 
gil

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

z/VSE Support Education and Manuals

[Jasi Grewal]

Hi, I have been requested to support z/VSE Platform, since I support z/VM and 
z/OS Systems.Since,  I have not used VSE systems for 40Yrs, I would be 
interested in learning any information which would help me support z/VSE 
Environments.
If you have any information which would help me then I would be really grateful.
Thank You in advance,Regards,Jasi Grewal.

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

ADR971E RC 8

[Mark Jacobs]

I got around the problem a different way, but I'd really like to understand why 
ADRDSSU won't restore(logically dumped) or copy a non-SMS extended addressable 
VSAM LDS dataset to an SMS managed extended addressable VSAM LDS. Is there 
something within the physical dataset that's different between it being SMS 
managed vs not being SMS managed?

Mark Jacobs

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

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

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

Re: Why is my second Rexx SYSCALLS read failing?

[Charles Mills]

Again, thanks everyone. The problem is solved. Just to respond to a couple of 
loose ends:

> I simply entered "REXX SYSCALLS OPEN" into Google Search

Yeah, me too. I got a different manual,

> Why does it always fail on the second file regardless of swapping  the order?

The file names are constructed by the program. Each file covers one month. The 
user specifies a date range and the program constructs the appropriate file 
names. It was getting the first one right but subsequent ones wrong. If you 
want the gory details, the filenames are of the form Foo-2022-09 and for the 
second file it was computing Foo-2022-9, not -09. I was displaying the 
constructed filename and Foo-2022-9 looks right to a human, not so much to the 
UNIX file system.

> I'll suggest defending against perverse file names 

The file names are constructed by the program and should never be perverse. 
They are not user input.

> That should make -21 impossible.

The -21 was on the read, not the open, and was appropriate.

I find the documentation very lacking in "big picture." The examples are often 
nearly useless. Is that (FN) syntax documented anywhere? I take it that the 
parentheses dereference FN so that the filename is the value of FN, not "FN" 
literally. Is that documented anywhere? Is there a SHARE presentation or 
anything like that that gives a big picture and some seriously useful examples?

Charles

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

z/OSMF and Health Checker butting heads

[Tom Longfellow]

I recently managed to get my z/OS Consoles support configured correctly to work 
under z/OSMF.

NOW, I am getting health checker hits on 
CHECK(IBMCNZ,CNZ_CONSOLE_MSCOPE_AND_ROUTCODE) 

I have tinkered with my EMCS definitions and even tried setting them to the 
z/OSMF recommended defaults.

I can see that is probably a MSCOPE or xROUT issue, but I can find no 
documented set of values that will please both products.   What MUST z/OSMF 
have for functionality?   What values will satisfy Health Checker??

My gut reaction is to kill the health check because it is totally unhelpful 
towards a resolution.   It says what is 'bad'  but gives no indication what is 
'good'.

Any suggestions on a functional solution that would quell this conflict?

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

Re: bpxpqrmxx and $SYSNAME vs

[Steve Smith]

The examples from the FM seem to generally use &-symbols when available,
and $-symbols when not.  $VERSION for example isn't a system-provided
symbol, although I assign it from 

On a rather tangential rant, I am annoyed with people who gratuitously
stuff $$$ all over in volsers, dsnames, and anything else they get their
hands on, evidently just because they think $$$ are so sexy.  Inside USS,
these become extremely annoying in trying to figure out the required
escapage.

sas


On Mon, Sep 12, 2022 at 11:15 AM Carmen Vitullo  wrote:

> I know the $SYSNAME. resolves to the system name but in my BPXPRMxx
> member I use //etc and //var
>
> I use /$VERSION for my mount-point for the SYSRES specific mount point
> for the version ROOT
>
> Carmen
>
>

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

Re: z/OSMF - again, next issue

[Shaffer, Terri]

Just remember, A CBPDO, doesn’t have to be processed as such, Receive it like 
normal, which will load the REL files, Then just APPLY/ACCEPT the FMID.

If you need the other files/doc they are there.  We seem to have lost the 
basics..

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide – Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Colin Paice
Sent: Tuesday, August 30, 2022 9:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: z/OSMF - again, next issue

EXTERNAL EMAIL: Do not click links or open attachments unless you know the 
content is safe.


I used to have to struggle with IBM installation manager - a package for 
installing software on midrange machines.
I remember being in a hotel trying to download a fix - but Installation
Manager(IM) decided it needed to upgrade itself before doing anything.  It took 
over 6 hours to download the new version of the Installation manager, and 
another 2 hours to download the fix I needed!  ( I had to set my alarm for 3 
am, and 5 am to click "go"  on the install)

IBM's argument was you only need to learn one interface (IM) to install 
software ( across Windows and Unix) - not realising I needed to know Windows, 
Unix AND IBM's IM.

z/OSMF is inevitable - Question: where are the skills of today?  Answer:
Java.

Personally I would follow the ADCD approach and download a volume of product 
libraries and its SMP/E  environment (and never use the SMP/E
environment)

Colin

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

 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 

This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

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

Re: bpxpqrmxx and $SYSNAME vs

[Carmen Vitullo]

I know the $SYSNAME. resolves to the system name but in my BPXPRMxx 
member I use //etc and //var


I use /$VERSION for my mount-point for the SYSRES specific mount point 
for the version ROOT


Carmen

On 9/11/2022 11:43 PM, Lizette Koehler wrote:

I have a coworker saying we should change our //etc/..   To
/$SYSNAME/etc/.

  


I am not familiar with coding this way

  


Could someone provide a cons vs pros (simple words please) on which is
needed, or used or preferred?

  


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

z/OS ISPF Git Interface (ZIGI) Version 3.15 Released

[Lionel B. Dyck]

We have released version 3.15 of ZIGI - the z/OS ISPF Git Interface.

You can find it at 
 - https://zigi.rocks
or
- https://cbttape.org/ftp/updates/CBT997.zip

Enjoy

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

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

Re: Real fun for companies on older machines & SCRT

[John McKown]

Problem resolved by using the Windows SCRT program to process the SMF data.
I tested this yesterday & it worked fine. I assume version 29 on Windows
will be available 15Oct2022 just like the z/OS version.

Actually, this won't be a problem until version 29 of SCRT is required.

On Mon, Sep 12, 2022, 00:33 Timothy Sipples  wrote:

> John, a couple questions from me:
>
> 1. What release of z/OS? 2.1?
>

1.12


> 2. What's your Java release? (java -version should tell you.)
>

Java 7. Upcoming SCRT requires Java 8. Java 8 won't run on our z9 due to
ALS level.


> 3. What's the exact, complete error message you're getting?
>

Sorry, I don't have the output anymore.


> — — — — —
> Timothy Sipples
> Senior Architect
> Digital Assets, Industry Solutions, and Cybersecurity
> IBM zSystems/LinuxONE, Asia-Pacific
> sipp...@sg.ibm.com
>
>
> --
> 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