Using quotes around the DSNAME will allow any combination of Hex chars for a
Dsname I think (possibly excluding 44X'04' which represents the VTOC). However
these are not supported for SMS datasets, nor can they be catalogued, nor can
they be protected by RACF.
https://www.ibm.com/docs/en/zos/3.1
I believe these came in with the re-write of the JCL Converter and/or
Interpreter which occurred with MVS 4.2 (working purely from memory!)
Lennie Dymoke-Bradshaw
https: //rsclweb.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: 07 January 20
W dniu 07.01.2024 o 21:55, Paul Gilmartin pisze:
On Sun, 7 Jan 2024 21:04:48 +0100, Radoslaw Skorupka wrote:
...
I have to admit: I almost never used DCB keyword in JCL and (AFAIR)
absolutely never DCB=HLQ.DATASET.NAME.
When teaching JCL I explain it, but also advice to not using that.
BTW:
W dniu 08.01.2024 o 05:01, Paul Gilmartin pisze:
On Mon, 8 Jan 2024 03:42:05 +, Gibney, Dave wrote:
Before LIKE, you needed IDCAMS to create VSAM files, after LIKE you could do
this with just JCL
Ah. So for PS or PO it has no advantage over DCB=dsname. Perhaps for SPACE?
A lot of adv
I have a PDS with configuration definitions in it and want to make it easy
to configure.
I want to have PDS members with content like PERMIT ... ACCESS(READ)
CLASS(...) ID(&ID)
and want the &ID to be substituted for example in JCL // SET ID=COLIN, and
be able to change the value on each run.
Howev
Colin,
I do it using IEBGENER:
// JCLLIB ORDER=pds.with.members.to.use
//SETSTEP EXEC PGM=IEBGENER
//SYSINDD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD *,SYMBOLS=JCLONLY
// INCLUDE MEMBER=x
//SYSUT2 DD DISP=SHR,DSN=dataset.to.contain.resolved.member
I don't know if thi
On Mon, 8 Jan 2024 at 12:16, Colin Paice wrote:
> I have a PDS with configuration definitions in it and want to make it easy
> to configure.
>
> I want to have PDS members with content like PERMIT ... ACCESS(READ)
> CLASS(...) ID(&ID)
> and want the &ID to be substituted for example in JCL // SET
CPPUPDTE (nee IPOUPDTE) only changes a existing member; the easiest ways I can
think of to do what you want are ISPF file tailoring or JCL substitution with a
// INCLUDE. I would probably go with the former.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְ
I believe that GDG model DSCBs are still a thing for non-SMS volumes.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Steve Thompson
Sent: Su
L?
I would expect 8X'FF' to work for PDSE, but what happens with PDS?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Steve Beaver <050e0
I don't know of any difference in expressive power and, no, you can't use it
with a path.
ObVir I don't find Q and QQ to be mnemonic. YMMV.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
Fro
On Mon, 8 Jan 2024 11:00:38 -, Lennie Dymoke-Bradshaw wrote:
>Using quotes around the DSNAME will allow any combination of Hex chars for a
>Dsname I think (possibly excluding 44X'04' which represents the VTOC). However
>these are not supported for SMS datasets, nor can they be catalogued, no
>> I have a PDS with configuration definitions in it and want to make it easy
>> to configure.
Colin,
You could use DFSORT to do the substitution and generate the control cards
which can be passed to the next steps that really execute the commands.
For example
// SET ID=COLIN
//*
//STEP0100 EX
Why the use of data set names enclosed with apostrophes, that are
not TSO oriented?
Back in the days when I was doing DOS to MVS migrations, to
access certain DOS data sets, you needed this because they could
contain names like this:
'PAYROLL STR 12MAY75' for either a Tape label or disk DSN.
DIRF.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Steve Thompson
Sent: Monday, January 8, 2024 11:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Su
It is common for IBM manuals for one component to give incorrect rules for
another component instead of referring the reader to the relevant
documentation. This is especially common when describing REXX or JCL
requirements for using that component.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.e
On Mon, 8 Jan 2024 14:22:42 +, Seymour J Metz wrote:
>CPPUPDTE (nee IPOUPDTE) only changes a existing member; the easiest ways I
>can think of to do what you want are ISPF file tailoring or JCL substitution
>with a // INCLUDE. I would probably go with the former.
>
Oh my! Can an INCLUDE st
Thanks!
I don't see the artifacts for the 9.6p1 build. Do the project
maintainers need to cut a release?
-- R; <><
On 1/5/24 20:04, kekronbekron wrote:
You could grab the latest (unsupported) release from this repo, once it's
published.
Here's a link to the pull request, which introduces t
Sri h Kolusu suggest the INCLUDE; I assume that he tested it. IMHO file
tailoring is a more versatile solution.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion L
>> Sri h Kolusu suggest the INCLUDE; I assume that he tested it. IMHO file
>> tailoring is a more versatile solution.
Shmuel,
Slight Correction. It is NOT me who suggested the INCLUDE solution. It is by
Charles hardee
https://www.mail-archive.com/ibm-main@listserv.ua.edu/msg135276.html
The s
Good catch Gil!
The one thing I forgot to say was that the member being included needs a
statement like this as the first entry:
// DD *,SYMBOLS=JCLONLY
Sorry for the confusion.
C-
On Mon, Jan 8, 2024 at 10:47 AM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote
CPPUPDTE (nee IPOUPDTE) cannot be used if your environment uses Endeavor. It
Will break ever pds that has had used Endeavor
Steve
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Hardee
Sent: Monday, January 8, 2024 12:39
Sorry for the delay. Holidays and family and friends and such. Ahhh...
It's been a minute, but I used SSH to carry PPP traffic back in the day.
The client side PPPD ran 'ssh' as a child process, arranging stdin and
stdout, as if it was a dial-up modem.
The server side ran the counterpart 'pppd'
On Mon, 8 Jan 2024 12:39:17 -0600, Charles Hardee wrote:
>
>The one thing I forgot to say was that the member being included needs a
>statement like this as the first entry:
>
>// DD *,SYMBOLS=JCLONLY
>
An alternative might be to concatenate JCL and the subject member into INTRDR.
In eit
Thanks for the heads-up.
I have added OpenSSH 9.6p1 to the Chicory collection.
Sadly, I don't have a z/OS build system for that collection. (And if
anyone can offer such, please pardon my sound-byte responses up to now.)
Had to bump-up the minimum level of OpenSSL from 1.0.2 to 1.1.1.
It builds
After getting an abend with SDWAEC2 (different from SDWAEC1) I observed
SDWAXFLG to be X'92' that means SDWAEC2 psw came from the linkage stack
Looking at the STCB field STCBLSDP I started going back ward by X'128' a
linkage stack entry and was unable to find a marching PSW
THANKS
-Ori
Yup, just post a comment on the PR, requesting a release.
On Monday, January 8th, 2024 at 22:36, Rick Troth wrote:
> Thanks!
>
> I don't see the artifacts for the 9.6p1 build. Do the project
> maintainers need to cut a release?
>
> -- R; <><
>
>
>
> On 1/5/24 20:04, kekronbekron wrote:
>
On 9/01/2024 6:26 am, Rick Troth wrote:
It's been a minute, but I used SSH to carry PPP traffic back in the day.
The client side PPPD ran 'ssh' as a child process, arranging stdin and
stdout, as if it was a dial-up modem.
I think this is difficult on z/OS because by default stdin and stdout
On Mon, 8 Jan 2024 at 19:20, Joseph Reichman wrote:
> After getting an abend with SDWAEC2 (different from SDWAEC1) I observed
> SDWAXFLG to be X'92' that means SDWAEC2 psw came from the linkage stack
>
> Looking at the STCB field STCBLSDP I started going back ward by X'128' a
> linkage stack entr
Depending on the use case https://www.stunnel.org can also be used exactly
for this purpose.
Cheers,
FP
wt., 9 sty 2024 o 12:01 Andrew Rowley
napisał(a):
> On 9/01/2024 6:26 am, Rick Troth wrote:
> >
> > It's been a minute, but I used SSH to carry PPP traffic back in the day.
> > The client sid
Thanks all I did was decrement X’128’
> On Jan 8, 2024, at 10:08 PM, Tony Harminc wrote:
>
> On Mon, 8 Jan 2024 at 19:20, Joseph Reichman wrote:
>
>> After getting an abend with SDWAEC2 (different from SDWAEC1) I observed
>> SDWAXFLG to be X'92' that means SDWAEC2 psw came from the linkage st
Which level recovery routine?
On Mon, 8 Jan 2024 19:19:59 -0500 Joseph Reichman
wrote:
:>After getting an abend with SDWAEC2 (different from SDWAEC1) I observed
SDWAXFLG to be X'92' that means SDWAEC2 psw came from the linkage stack
:>
:>Looking at the STCB field STCBLSDP I started going back
32 matches
Mail list logo
