John, a couple questions from me:
1. What release of z/OS? 2.1?
2. What's your Java release? (java -version should tell you.)
3. What's the exact, complete error message you're getting?
— — — — —
Timothy Sipples
Senior Architect
Digital Assets, Industry Solutions, and Cybersecurity
IBM zSystems
Since $ is a valid character in a SYSNAME, I dont think you want to make
that change.
Joe
On Sun, Sep 11, 2022 at 11:44 PM Lizette Koehler
wrote:
> I have a coworker saying we should change our /&SYSNAME/etc/.. To
> /$SYSNAME/etc/.
>
>
>
> I am not familiar with coding this way
>
>
>
> Could
I have a coworker saying we should change our /&SYSNAME/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
I figured out which manual he was citing. The new lines are needed in order for
the commas to be valid. Similarly, the new lines between statements are needed
because the are no explicit semicolons. The example in the manual is correct if
you don't mess with the line breaks.
Note that the expre
Those are commands, not functions.
From: IBM Mainframe Discussion List on behalf of
Farley, Peter x23353 <031df298a9da-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, September 11, 2022 2:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why is my second R
You're welcome.
I simply entered "REXX SYSCALLS OPEN" into Google Search, and this was
the first hit:
https://www.ibm.com/docs/en/zos/2.1.0?topic=commands-open-write-close-file
this is where I found the sample code.
I didn't know or use SYSCALLS before.
Kind regards
Bernd
Am 11.09.2022 um
On Sat, Sep 10, 2022 at 7:05 PM Michael Oujesky
wrote:
> Look like LINUX desktops are supported and simple binary transfer of
> the SMF data per
> <
> https://www-40.ibm.com/servers/resourcelink/svc00100.nsf/pages/SCRTsc236845/$file/e0z3s127.pdf>SCRT:
>
> Using the Sub-Capacity Reporting Tool V28
On Sat, 10 Sep 2022 18:45:04 -0500, Charles Mills wrote:
>...
>... the first file works (and the second file works if it is first).
>
On Sun, 11 Sep 2022 11:29:07 -0500, Charles Mills wrote:
>Thank you all and especially @Bernd Oppolzer. They key is that I was not
>checking the open for
On Sun, 11 Sep 2022 18:11:11 +, Farley, Peter x23353 wrote:
>The RC values are documented here for all SYSCALLS functions (including -21,
>-22, ...):
>
>https://www.ibm.com/docs/en/zos/2.5.0?topic=values-returned-from-syscall-environment
>
Thanks. I missed that. Very similar convention to
The RC values are documented here for all SYSCALLS functions (including -21,
-22, ...):
https://www.ibm.com/docs/en/zos/2.5.0?topic=values-returned-from-syscall-environment
Note though that there is also language saying that various "other" RC values
can be produced by "some" functions without
On Sun, 11 Sep 2022 11:29:07 -0500, Charles Mills wrote:
>... Bad open of course yields a bad fd which yields a -21. It is all new
> code and I had not tested open failures specifically.
>
>Not sure where you saw the example that you cited. The IBM doc that I am
>looking at has the followin
Thank you all and especially @Bernd Oppolzer. They key is that I was not
checking the open for success correctly. I was formatting the second file name
incorrectly and as a result the open was failing but my code did not make me
aware of that. Bad open of course yields a bad fd which yields a -2
On Sun, 11 Sep 2022 12:15:37 +, Seymour J Metz wrote:
>Comma isn't a valid delimitor in an expression. Did you mean
>'open' path', O_rdwr+O_creat+O_trunc, 660'
>?
There was no such comma in Charles's original (pseudo?)code.
Bernd noted that he had problems copying from "the IBM doc"
with no
What I see is multiple lines, with a new line after the comma, making the comma
a continuation character. For that to be valid on a single line you must remove
the comma and insert semicolons to separate statements.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
_
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 in
Comma isn't a valid delimitor in an expression. Did you mean
'open' path', O_rdwr+O_creat+O_trunc, 660'
?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Bernd Oppolzer
If you LOAD02 is in SYS.IPLPARM, then like Mike Babcock said, use the DSN parm.
SETLOAD 02,IEASYM,DSN=SYS.IPLPARM
I do this all the time.
Richard McIntosh
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Michael Babcock
Sent: Saturday, September 10, 2022 10:39 PM
To
On Sun, 11 Sep 2022 10:02:53 +0200, Bernd Oppolzer wrote:
>Once again wrong, my e-Mail client is fooling me. Next try:
>
It's way hard nowadays to Copy/Paste from manuals preserving formatting.
>'open' path, O_rdwr+O_creat+O_trunc, 660
>if retval=-1 then do
> say 'file not opened, error code
Once again wrong, my e-Mail client is fooling me. Next try:
'open' path, O_rdwr+O_creat+O_trunc, 660
if retval=-1 then do
say 'file not opened, error codes' errno errnojr
return
end
fd=retval
Am 11.09.2022 um 10:01 schrieb Bernd Oppolzer:
sorry for the strange formatting of the example
sorry for the strange formatting of the example code:
should be
'open' path, O_rdwr+O_creat+O_trunc, 660
if retval=-1 then do
say 'file not opened, error codes' errno errnojr return
end
fd=retval
Kind regards
Bernd
Am 11.09.2022 um 09:57 schrieb Bernd Oppolzer:
Why is there suddenly the
Why is there suddenly the variable RC used to test the outcome of OPEN?
In the examples in the IBM doc I see:
|'open' path, O_rdwr+O_creat+O_trunc, 660 if retval=-1 then do say 'file
not opened, error codes' errno errnojr return end fd=retval |that is:
the returned fd and the code to test the
21 matches
Mail list logo
