Re: How can I keep JES2 from being SYSPLEXed?

2024-01-21 Thread Paul Feller
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'm glad things 
are now working for you.


Paul

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wendell Lovewell
Sent: Sunday, January 21, 2024 3:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How can I keep JES2 from being SYSPLEXed?

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 was that they not be part 
of the same MAS. 

Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems 
to come up, apparently independently of each other.  (I used JES2Z3 on my S0W3 
system and JES2Z4 on my S0W1 system.)

I did a cold start on the S0W3 JES, and these Groups/Members were used:
GROUP SYSJES MEMBER S0W3  
GROUP JES2Z3  MEMBER JES2$S0W3 
GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$  

I did not do a cold start on the S0W1 JES, and I believe it used the 
former/default value: 
GROUP SYSJES MEMBER S0W1
GROUP JES2  MEMBER JES2$S0W1   
GROUP SYSJ2$XD MEMBER JES2$S0W1$$$


Thanks again,
Wendell

--
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: C++ and Linker/Binder parameters for "called as subprogram"

2024-01-21 Thread Charles Mills
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 not 
in C++ and LE -- it's in the COBOL compiler calling exits! Here are the numbers 
-- CPU seconds, details below -- for various situations:

NOADATA: 1.91 CPU seconds
ADATA to DUMMY: 1.935 CPU seconds
ADATA to DASD: 2.04 CPU seconds
ADATA to DUMMY, 3-instruction exit: 2.82 CPU seconds -- an overhead of over 45 
percent!

Details: REGION=0M, COBOL 6.2, up-to-date on PTFs, typical options, OPT(0), 
52,063 lines, 34,012 statements, z14-M01, TCB+SRB time per IEF033I. All tests 
run on a reasonably quiet LPAR.

Gr!

Charles

On Sat, 30 Dec 2023 16:36:07 -0600, Charles Mills  wrote:

>I have a working Enterprise COBOL compiler exit written in XLC C++. It 
>functions "correctly" but it is consuming more CPU time than expected, and I 
>have this suspicion that it is going through LE initialization on each entry.
>
>The COBOL doc says of exit modules "The Enterprise COBOL compiler 
>automatically manages a preinitialized Language Environment at compile time, 
>and calls compiler exits within this environment. Therefore, the following 
>rules apply: Compiler exits are run as subprograms instead of main programs. 
>Compiler exits must not include logic for explicitly initializing or 
>terminating Language Environment."
>
>I have not done anything real special in the C++ code. My entry point is *not* 
>a "main" function and is declared extern "OS" void. I am pre-binding and 
>linking pretty much as I have done for other C++ programs. I tell the binder 
>simply INCLUDE, ENTRY and NAME with no reference to CEESTART.
>
>Is there something "special" that I should be doing differently?
>
>Phrasing the question differently, if an LE program loads an LE program by 
>module name and then calls it, how should that called program be compiled and 
>bound so as to avoid repeated LE initialization?

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


Re: How can I keep JES2 from being SYSPLEXed?

2024-01-21 Thread Wendell Lovewell
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 was that they not be part 
of the same MAS. 

Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems 
to come up, apparently independently of each other.  (I used JES2Z3 on my S0W3 
system and JES2Z4 on my S0W1 system.)

I did a cold start on the S0W3 JES, and these Groups/Members were used:
GROUP SYSJES MEMBER S0W3  
GROUP JES2Z3  MEMBER JES2$S0W3 
GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$  

I did not do a cold start on the S0W1 JES, and I believe it used the 
former/default value: 
GROUP SYSJES MEMBER S0W1
GROUP JES2  MEMBER JES2$S0W1   
GROUP SYSJ2$XD MEMBER JES2$S0W1$$$


Thanks again, 
Wendell

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


Re: Masking SMF data internally

2024-01-21 Thread Michael Oujesky

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, 2024, 10:26 AM ITschak Mugzach  wrote:

> Are these files machine or human readable? As you can edit them, I believe
> they are human readable and no Hex data inside. If so, write a rexx to
> translate everything a-z to blanks and write back.
>
> ITschak
>
> *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere
> Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux
> and IBM I **|  *
>
> *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|*
> *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il  **|*
>
>
>
>
>
> בתאריך יום א׳, 21 ×‘×™× ×•×³ 2024 ב-7:59 מאת Jake Anderson <
> justmainfra...@gmail.com>:
>
> > Hello
> >
> > We have a requirement of sharing our SMF data to vendor for a sizing
> > operation of our hardware connected to our mainframe
> >
> >
> > Our organization has a policy of masking the critical values before
> sharing
> > it. I see SMF datasets are are editable from ISPF.
> >
> > Is there a way or someone has undergone this exercise of masking the
> > confidential values inside SMF output Dataset?
> >
> > Please advise
> >
> > Jake
> >
> > --
> > 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 create a vsam dataset with an akuas

2024-01-21 Thread Seymour J Metz
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 Mainframe Discussion List  on behalf of 
Lizette Koehler 
Sent: Sunday, January 21, 2024 4: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) 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.


--
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: Masking SMF data internally

2024-01-21 Thread Paul Feller
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 Message-
From: IBM Mainframe Discussion List  On Behalf Of
Binyamin Dissen
Sent: Sunday, January 21, 2024 1:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Masking SMF data internally

On Sun, 21 Jan 2024 09:58:29 +0400 Jake Anderson 
wrote:

:>We have a requirement of sharing our SMF data to vendor for a sizing
:>operation of our hardware connected to our mainframe

:>Our organization has a policy of masking the critical values before
sharing :>it. I see SMF datasets are are editable from ISPF.

:>Is there a way or someone has undergone this exercise of masking the
:>confidential values inside SMF output Dataset?

First identify which types and subtypes are required. That will reduce the
job and may make it trivial.

--
Binyamin Dissen  http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

--
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 create a vsam dataset with Alias

2024-01-21 Thread Steve Horein
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))

https://www.ibm.com/docs/en/zos/2.5.0?topic=commands-define-path

On Sun, Jan 21, 2024 at 3:47 AM Lizette Koehler 
wrote:

> 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
>

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


Re: How to create a vsam dataset with Alias

2024-01-21 Thread Lizette Koehler
-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) 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.


--
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


How to create a vsam dataset with an akuas

2024-01-21 Thread Lizette Koehler
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.


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