Okay this wakes up some retired brain cells. Because tasks communicate across
XCF (even when you don't know about it) they have to have a unique identifier
for things to work properly. Some tasks will create a unique identifier by
default and some will not. I forgot about that little item.
I wanted to close the loop on this, and frankly, vent a little bit.
I played around and played around with different C++ and LE options -- nothing
seemed to make a big difference. So finally I wrote a trivial, 3-machine
instruction, do-nothing ADATA exit in HLASM. It turns out the overhead is
Thanks for your help Bruce and Paul.
I was able to ask this to the IBM support team and they told me about the
"XCFGRPNM" parm on the JES2 MASDEF statement.
I hadn't specified a value for this, so both were using the default of "JES2".
This was causing the conflict, even though my intent
REVIEW (CBT134) can at least browse SMF VBS files.
Michael
At 12:43 AM 1/21/2024, Jake Anderson wrote:
I am not even able to browse
It says 'Invalid record length'. I tried setting the block size and LRECL
but by default it takes as
Record length': 32767
Block size : 32760
On Sun, Jan 21,
It's DEFINE PATH. I have no idea why DEFINE ALIAS is only for non-VSAM. What
happens if you have duplicate DEFINE CLUSTER commands?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM
Jake, I agree you need to identify what record types are needed for the
sizing operation. After you know which record types (and subtypes) you may
not need to do anything. As an example, I can't think of any sensitive data
that might be in the SMF type 7x records.
Paul
-Original
I believe PATH will accomplish what you want to do. I found this bit of JCL
from when I lead a different life:
//CATLG1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSINDD *
DEF PATH(NAME(SYST.MOBIUS.VIEWDIR.SCREENS) -
PATHENTRY(SYST.MOBIUS.VIEWDIR.LX0783.SCREENS))
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lizette Koehler
Sent: Sunday, January 21, 2024 2:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: How to create a vsam dataset with an akuas
I have a VSAM data set called VSAM1
I want to have it have another name (alias)
I have a VSAM data set called VSAM1
I want to have it have another name (alias) called VSAMTST
So if a user has NAME=VSAM1 or NAME=VSAMTST
Both HLQs will be I the same usercat
It all accesses the same VSAM dataset VSAM1
What is the best way to do that?
Thank you.
