Hi Peter,
enjoy your retirement.
I'm sure all the community will miss you and your valuable contributions.
Max
Il giorno ven 3 gen 2025 alle ore 16:15 Peter Relson <
056a472f7cb4-dmarc-requ...@listserv.ua.edu> ha scritto:
> Hi, IBM-Mainers.
> I am retired as of January 1.
> I'll likely lurk
Possibly, I will have to check to see for sure, but it might.
Brian
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Take a look at the fixcds command.
https://www.ibm.com/docs/en/zos/3.1.0?topic=commands-maintenance-command-fixcds
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
On Monday, January 6
The ARC0743I indicates the data set/version which was used to backup the CDS or
journal to. There should also be an ARC0748I which indicates what the data
set/version was renamed to.
To make these non-sms data sets you will need to update your SMS ACS routines.
Max Smith
DFSMS Development
Hi all,
I am running a HSM AUDIT DSCTL(BACKUP), which is ending with a few ERR 39:
ERR 39 dataset name IS MISSING, with a lot of dots afterward. When I
execute the LIST BCDS LEVEL (dataset name) command, it wil display, for a
ten generation backup, seven good backups and three error lines "ARC0184I
Classification: Confidential
The name is "fixed" by the ARCCMD00 parameters. These datasets can be managed
as non-sms.
You need to pre-allocate these datasets prior to use.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Peter
Sent: Monday, December 23, 2024 5:48 AM
Classification: Confidential
Does the SAPI interface not provide that information?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Brian Westerman
Sent: Sunday, December 22, 2024 12:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Get access to the $HCT in JES2
[CAUTION:
I looked at the RCVT mapping at
https://www.ibm.com/docs/hr/zos/3.1.0?topic=zssrda-rcvt-racf-communication-vector-table
The structure length stated as 2038 (0 (0) STRUCTURE 2038 RCVT LOCATED
THROUGH CVT) by the last entry is at 2308 (not 2038: 2308 (904) CHARACTER
* END OF RCVT
Is it a typo (I b
