Re: Request for ISV SMF Usage
Have you looked at MXG? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Cheryl Watson [che...@watsonwalker.com] Sent: Wednesday, May 20, 2020 9:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Request for ISV SMF Usage At the request of the MVSP project of SHARE several years ago, I created a list of all SMF record types from both IBM and ISVs. I posted it here - https://secure-web.cisco.com/1Yflw6CA-zTRZlmTTOOfkJcViiQ_elDkrN-lnMBl6gA-wZBApk1wSE457xesW9eXSxQZlocCDev2JLB-mN3atNoFQryL3snNwJpvE95eb91Cky5Amp-457xyqY62HKr1U-5TZQWXKZm3fRjh0ASWSwgohBOnJn1av8cXQSmyN37jGe1LWDRfJs5pIlso-9T99DIPVyQAEwWTbxnS0NRS9D8nyphlgf2nKiscpXrm3Up1m6J53dM46xTLejgxA098FyCS-lUwOy0qQdNyj5-3ULTilifnjIyq4D9eQIJlt3jbL6onoKLoi8vefM_e1LEqqRX9AL-oLWMFDzGmMlSYrLvMevCxUaR7c3v0EoDIrCF7QTgHz0VDpU1es-SCaNHnnaECPND10GwgEQnPu32D9bwFUGjemqr6E_JPP3nsbvI-fX25t0iu0w9CB5EcxOFO9/https%3A%2F%2Fwatsonwalker.com%2Fpublications%2F#smf. I didn't update it last year due to illness and travel, but I am now in the process of updating it to include z/OS 2.3 and 2.4, and would like to include as many as possible of ISV products that create SMF records. Many of my usual ISV contacts have since left and I would like to reach out to you to pass my request to anyone in your organization who could help. Just have them contact me at technical at watsonwalker.com. Many thanks! Cheryl Watson Watson & Walker, Inc. -- 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
Request for ISV SMF Usage
At the request of the MVSP project of SHARE several years ago, I created a list of all SMF record types from both IBM and ISVs. I posted it here - https://watsonwalker.com/publications/#smf. I didn't update it last year due to illness and travel, but I am now in the process of updating it to include z/OS 2.3 and 2.4, and would like to include as many as possible of ISV products that create SMF records. Many of my usual ISV contacts have since left and I would like to reach out to you to pass my request to anyone in your organization who could help. Just have them contact me at technical at watsonwalker.com. Many thanks! Cheryl Watson Watson & Walker, Inc. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Why ICH0007I and how fix?
RALTER RACFVARS ADDMEM(mynode) SETROPTS RACLIST(RACFVARS) REFRESH and the problem went away! Thank you. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lou Losee Sent: Wednesday, May 20, 2020 2:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Why ICH0007I and how fix? You add the node where node is the local JES node name as a member in the profile in the RACFVARS class. All this does is specify that the node is local to the RACF data base. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: What crashing COBOL systems reveal about applications maintenance -- GCN
We setup for OPT(1) because IBM said that was the thing to do initially. We’ve only recently been told to go OPT(2). We’ve also run into an interesting issue of COBOL 6.2 compiles using OPT(0) taking > 10x CPU of same compile with 4.2. I don’t recall being told that we would see that level of CPU burn for planning for capacity for migrating to 6.2. Regards Steve Thompson --- frank.swarbr...@outlook.com wrote: From: Frank Swarbrick To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] What crashing COBOL systems reveal about applications maintenance -- GCN Date: Wed, 20 May 2020 21:28:33 + We use OPT(1). Probably for no good reason. (And it was my decision, meaning its easy enough to change!) From: IBM Mainframe Discussion List on behalf of Tom Ross Sent: Wednesday, May 20, 2020 3:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What crashing COBOL systems reveal about applications maintenance -- GCN >Suppose that they took a group of programmers and got the production online= > programs to all compile with COBOL 6.2 and OPT(1). Would they see a signif= >icant reduction in MSUs? Assuming they are running on z14s minimally? I sure hope no one is using OPT(1) with 3rd generation COBOL! IBM expects all users to compile with OPT(2) for production performance. I am honestly not sure why we shipped OPT(1). Users should use OPT(0) if they want more straight-forward debugging (no optimizations) and then after unit test compile with OPT(2) for performance, and and never use OPT(1). Alternatively, they could compile with OPT(2) for debugging and get used to odd things like statements getting moved or deleted while debugging. Cheers, TomR >> COBOL is the Language of the Future! << -- 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: Why ICH0007I and how fix?
You add the node where node is the local JES node name as a member in the profile in the RACFVARS class. All this does is specify that the node is local to the RACF data base. Lou -- Artificial Intelligence is no match for Natural Stupidity - Unknown On Wed, May 20, 2020 at 4:21 PM Charles Mills wrote: > I asked this question this morning on RACF-L and got not a whimper. Perhaps > it is a JES2 question and not a RACF question? > > I am issuing a JES2 $DQ command from a Rexx EXEC running under IKJEFT01. It > is all working but for every command issued I am getting > > ICH70007I USER AUTHORITY CANNOT BE USED FOR THIRD-PARTY > AUTHORIZATION CHECK FOR USER (userid ) GROUP (SYS1) > BECAUSE THE EXECUTION NODE (mynode) IS NOT LOCAL. > UACC WILL BE USED. > > I have read the description of the message > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2 > .icha600/ich70007i.htm but I don't understand any more than I did before. I > am *not* getting ICH408I so I guess that is why it is all working. > > AFAIK 'mynode' *is* the local LPAR. I am not specifying any node in my > CONSOLE ACTIVATE/CART/ADDRESS CONSOLE. > > $HASP826 NODE(1) > $HASP826 NODE(1) NAME=mynode,STATUS=(OWNNODE),TRANSMIT=BOTH, > $HASP826 RECEIVE=BOTH,HOLD=NONE > > Can someone explain what the message means and how to make it go away? > > I see "make sure that the node is defined to the profile in the > RACFVARS class." How do I do that and what are the risks? > > As you can tell, I am not a RACF admin, only playing one in my spare time. > > Thanks, > Charles > > -- > 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: Why ICH0007I and how fix?
>From a thread in RACF from 2008 This message occurs when a token from one lpar may be used on another lpar. Do these lpars SHARE the same RACF database? If so then making each one LOCAL to the other is okay. If they DO NOT share the same DB then NODES profiles may be necessary to do userid/ group transaltion. >From the Racf Messages: Check to see if the execution node is supposed to be local. If it is, make sure that the node is defined to the profile in the RACFVARS class. Otherwise, only the UACC authority for the protected resource can be obtained. Does that help? Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Wednesday, May 20, 2020 2:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Why ICH0007I and how fix? I asked this question this morning on RACF-L and got not a whimper. Perhaps it is a JES2 question and not a RACF question? I am issuing a JES2 $DQ command from a Rexx EXEC running under IKJEFT01. It is all working but for every command issued I am getting ICH70007I USER AUTHORITY CANNOT BE USED FOR THIRD-PARTY AUTHORIZATION CHECK FOR USER (userid ) GROUP (SYS1) BECAUSE THE EXECUTION NODE (mynode) IS NOT LOCAL. UACC WILL BE USED. I have read the description of the message https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2 .icha600/ich70007i.htm but I don't understand any more than I did before. I am *not* getting ICH408I so I guess that is why it is all working. AFAIK 'mynode' *is* the local LPAR. I am not specifying any node in my CONSOLE ACTIVATE/CART/ADDRESS CONSOLE. $HASP826 NODE(1) $HASP826 NODE(1) NAME=mynode,STATUS=(OWNNODE),TRANSMIT=BOTH, $HASP826 RECEIVE=BOTH,HOLD=NONE Can someone explain what the message means and how to make it go away? I see "make sure that the node is defined to the profile in the RACFVARS class." How do I do that and what are the risks? As you can tell, I am not a RACF admin, only playing one in my spare time. Thanks, Charles -- 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: REXX and BPXWUNIX()
Some REXX basic:
1. REXX is strictly call by value. When you need a name, the caller has to
pass a string containing the name. So in your call to bpxwunix you need to pass
expressions evaluating to the names. In your case simple string literals will
do.
2. The name of a stem ends in a period. The string 'ipaddr.i' refers to a
compound variable in ipaddr., not to the stem.
3. There is a convention in REXX to simulate arrays using compound variable
with the subscript as the tail and for tail 0 to contain the number of
remaining elements.
So I assume that you need something like
address TSO /* not needed if already in TSO environment */
'Execio * Diskr input (STEM ipaddr. finis'
Do i = 1 to ipaddr.0
call bpxwunix 'host' ipaddr.i, , 'out.' /* extra comma because 'in.' is
omitted */
say 'inaddr ' ipaddr.i
say 'first output line ' out.1
'Execio 1 Diskw ddout (STEM out. '
End
"EXECIO 0 DISKW ddout (FINIS)"
Exit
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of J
Ellis [020d5fbe36e0-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, May 20, 2020 3:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: REXX and BPXWUNIX()
i would like to use the bpxwunix function to run, either HOST or DIG or
nslookup commands, seems pretty straightforward ...
but I can not get the put to com back to me, it has to be something silly i am
overlooking, any help would be appreciated
/* rexx */
say 'hostname running'
RC = SYSCALLS('ON')
If RC<0 | RC>4 Then Exit RC
address TSO 'Execio * Diskr input (STEM ipaddr. finis'
Address SYSCALL
Do i = 1 to ipaddr.0
call bpxwunix 'host ',ipaddr.i,out.
say 'inaddr ' ipaddr.i
say 'out ' out.
Address tso
'Execio 1 Diskw ddout (STEM out. '
End
"EXECIO 0 DISKW ddout (FINIS)"
Exit
the input is for example, the ipaddr.0 is number of lines, then the IP's i wish
to query.
2
8.8.8.8
8.8.4.4
for the host command under omvs/ishell, i get EZZ8321I dns.google has addresses
8.8.8.8
i am expecting that returned back to my out. stack
i get the same null results in TSO interactive as batch, here's the JCL
//@TSOSYSP EXEC PGM=IKJEFT01,REGION=8M,
// PARM='HOSTNAME'
//SYSEXEC DD DISP=SHR,DSN=SYSEXEC
//SYSTSPRT DD SYSOUT=*
//SYSTSINDD DUMMY,LRECL=80
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//DDOUT DD SYSOUT=*
//INPUT DD DISP=SHR,DSN=MYOMVS.PDSE(STDIN)
--
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: What crashing COBOL systems reveal about applications maintenance -- GCN
We use OPT(1). Probably for no good reason. (And it was my decision, meaning its easy enough to change!) From: IBM Mainframe Discussion List on behalf of Tom Ross Sent: Wednesday, May 20, 2020 3:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What crashing COBOL systems reveal about applications maintenance -- GCN >Suppose that they took a group of programmers and got the production online= > programs to all compile with COBOL 6.2 and OPT(1). Would they see a signif= >icant reduction in MSUs? Assuming they are running on z14s minimally? I sure hope no one is using OPT(1) with 3rd generation COBOL! IBM expects all users to compile with OPT(2) for production performance. I am honestly not sure why we shipped OPT(1). Users should use OPT(0) if they want more straight-forward debugging (no optimizations) and then after unit test compile with OPT(2) for performance, and and never use OPT(1). Alternatively, they could compile with OPT(2) for debugging and get used to odd things like statements getting moved or deleted while debugging. Cheers, TomR >> COBOL is the Language of the Future! << -- 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: What crashing COBOL systems reveal about applications maintenance -- GCN
>Suppose that they took a group of programmers and got the production online= > programs to all compile with COBOL 6.2 and OPT(1). Would they see a signif= >icant reduction in MSUs? Assuming they are running on z14s minimally? I sure hope no one is using OPT(1) with 3rd generation COBOL! IBM expects all users to compile with OPT(2) for production performance. I am honestly not sure why we shipped OPT(1). Users should use OPT(0) if they want more straight-forward debugging (no optimizations) and then after unit test compile with OPT(2) for performance, and and never use OPT(1). Alternatively, they could compile with OPT(2) for debugging and get used to odd things like statements getting moved or deleted while debugging. Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Why ICH0007I and how fix?
I asked this question this morning on RACF-L and got not a whimper. Perhaps it is a JES2 question and not a RACF question? I am issuing a JES2 $DQ command from a Rexx EXEC running under IKJEFT01. It is all working but for every command issued I am getting ICH70007I USER AUTHORITY CANNOT BE USED FOR THIRD-PARTY AUTHORIZATION CHECK FOR USER (userid ) GROUP (SYS1) BECAUSE THE EXECUTION NODE (mynode) IS NOT LOCAL. UACC WILL BE USED. I have read the description of the message https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2 .icha600/ich70007i.htm but I don't understand any more than I did before. I am *not* getting ICH408I so I guess that is why it is all working. AFAIK 'mynode' *is* the local LPAR. I am not specifying any node in my CONSOLE ACTIVATE/CART/ADDRESS CONSOLE. $HASP826 NODE(1) $HASP826 NODE(1) NAME=mynode,STATUS=(OWNNODE),TRANSMIT=BOTH, $HASP826 RECEIVE=BOTH,HOLD=NONE Can someone explain what the message means and how to make it go away? I see "make sure that the node is defined to the profile in the RACFVARS class." How do I do that and what are the risks? As you can tell, I am not a RACF admin, only playing one in my spare time. Thanks, Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX and BPXWUNIX()
On Wed, 20 May 2020 14:56:39 -0500, J Ellis
wrote:
>i would like to use the bpxwunix function to run, either HOST or DIG or
>nslookup commands, seems pretty straightforward ...
>but I can not get the put to com back to me, it has to be something silly i am
>overlooking, any help would be appreciated
>
>/* rexx */
>say 'hostname running'
>RC = SYSCALLS('ON')
>If RC<0 | RC>4 Then Exit RC
>address TSO 'Execio * Diskr input (STEM ipaddr. finis'
>Address SYSCALL
> Do i = 1 to ipaddr.0
>call bpxwunix 'host ',ipaddr.i,out.
>say 'inaddr ' ipaddr.i
>say 'out ' out.
> Address tso
> 'Execio 1 Diskw ddout (STEM out. '
> End
> "EXECIO 0 DISKW ddout (FINIS)"
> Exit
A refactoring (untested). See:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb600/wunix.htm
/* rexx */
say 'hostname running'
RC = SYSCALLS('ON')
If RC<0 | RC>4 Then Exit RC
empty.0 = 0 /* Empty stdin stem. */
address TSO 'Execio * Diskr input (STEM ipaddr. finis'
Do i = 1 to ipaddr.0
call bpxwunix 'host 'ipaddr.i '2>&1', , /* Redirect stderr to stdout. */
'empty.', 'out.'
say 'inaddr ' ipaddr.i
say 'out lines' out.0
Address tso
'Execio' out.0 'Diskw ddout (STEM out.)' /* Print all lines if more than 1.
*/
End
"EXECIO 0 DISKW ddout (FINIS)"
Exit
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX and BPXWUNIX()
On Wed, 20 May 2020 14:56:39 -0500, J Ellis wrote:
>i would like to use the bpxwunix function to run, either HOST or DIG or
>nslookup commands, seems pretty straightforward ...
>but I can not get the put to com back to me, it has to be something silly i am
>overlooking, any help would be appreciated
>
>/* rexx */
>say 'hostname running'
>RC = SYSCALLS('ON')
>If RC<0 | RC>4 Then Exit RC
>address TSO 'Execio * Diskr input (STEM ipaddr. finis'
>Address SYSCALL
>
Address SYSCALL is superfluous. BPXWUNIX is a function to
which host environment is irrelevant.
> Do i = 1 to ipaddr.0
>call bpxwunix 'host ',ipaddr.i,out.
>
No. BPXWUNIX should be called with a stem, such as "ipaddr.",
not "ipaddr.i".
>say 'inaddr ' ipaddr.i
>say 'out ' out.
> Address tso
> 'Execio 1 Diskw ddout (STEM out. '
> End
> "EXECIO 0 DISKW ddout (FINIS)"
> Exit
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
REXX and BPXWUNIX()
i would like to use the bpxwunix function to run, either HOST or DIG or
nslookup commands, seems pretty straightforward ...
but I can not get the put to com back to me, it has to be something silly i am
overlooking, any help would be appreciated
/* rexx */
say 'hostname running'
RC = SYSCALLS('ON')
If RC<0 | RC>4 Then Exit RC
address TSO 'Execio * Diskr input (STEM ipaddr. finis'
Address SYSCALL
Do i = 1 to ipaddr.0
call bpxwunix 'host ',ipaddr.i,out.
say 'inaddr ' ipaddr.i
say 'out ' out.
Address tso
'Execio 1 Diskw ddout (STEM out. '
End
"EXECIO 0 DISKW ddout (FINIS)"
Exit
the input is for example, the ipaddr.0 is number of lines, then the IP's i wish
to query.
2
8.8.8.8
8.8.4.4
for the host command under omvs/ishell, i get EZZ8321I dns.google has addresses
8.8.8.8
i am expecting that returned back to my out. stack
i get the same null results in TSO interactive as batch, here's the JCL
//@TSOSYSP EXEC PGM=IKJEFT01,REGION=8M,
// PARM='HOSTNAME'
//SYSEXEC DD DISP=SHR,DSN=SYSEXEC
//SYSTSPRT DD SYSOUT=*
//SYSTSINDD DUMMY,LRECL=80
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//DDOUT DD SYSOUT=*
//INPUT DD DISP=SHR,DSN=MYOMVS.PDSE(STDIN)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX assistance
It looks like the Netview IDCAMS command accepts at most two parameters
that must be DDNAMEs. The second DDNAME will default to SYSPRINT if not
specified. The DDNAMEs are basically INPUT and OUTPUT files. So the INPUT file
must be built prior to invoking the Netview IDCAMS command.
The DSIVSMX IDCAMS command also calls the IDCAMS utility, but the
IDCAMS control statements are read from the message that started the DSIVSMX
command. This is more conducive to being used within a PIPE with a STEM
variable as the input stream.
The Netview help for DSIVSMX IDCAMS (Option F) references those same
Netview samples; CNMS8013, CNMS8014, CNMS8015 and CNMS8020.
Also, the groups.io group or Netview can be found here:
https://groups.io/g/NetView
Hth
Tony
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jousma, David
Sent: Wednesday, May 20, 2020 1:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
[[ SEI WARNING *** This email was sent from an external source. Do not open
attachments or click on links from unknown or suspicious senders. *** ]]
Thanks Tony. I see that IDCAMS used within netview is a valid netview command.
But then I see this in the netview samplib
Define_Base_Cluster_VSAM_File:
/* Called by Define_and_Load_Base_Cluster*/
SAY 'Attempting to define the VSAM file'basename
k.0 = 14
k.1 = ' DEFINE CLUSTER -'
k.2 = ' (NAME ('basename') -'
k.3 = ' INDEXED -'
k.4 = ' KEYS('key_size RKP') -'
k.5 = ' SHAREOPTIONS('shr1 shr2') -'
k.6 = ' RECORDSIZE('avg_recsize max_recsize') -'
k.7 = ' VOLUMES(CPDLB2) -'
k.8 = ' NOREUSE ) -'
k.9 = ' DATA -'
k.10 = ' (NAME ('basename'.DATA) -'
k.11 = ' CYLINDERS('data_size') ) -'
k.12 = ' INDEX -'
k.13 = ' (NAME ('basename'.INDEX) -'
k.14 = ' CYLINDERS('index_size') )'
'PIPE STEM k.|COLLECT|NETV MOE DSIVSMX IDCAMS|STEM R1.'
What purpose is the last line, specifically the NETV MOE DSIVSMX IDCAMS
portion? Why not just NETV MOE IDCAMS?According to the fine manual
DSIVSMX is labelled as a "command processor". Does that imply setting up an
environment? I've asked IBM these questions too.
IBM Tivoli NetView for z/OS, Version 6.2 The DSIVSMX command processor can
define, read, and write VSAM keyed files directly from REXX without using data
services tasks. This enables the implementation of VSAM applications, including
end-use application development in REXX (in conjunction with the pipeline
facility), and intensive VSAM diagnostics.
The DSIVSMX command provides REXX access to keyed VSAM files and to IDCAMS, the
VSAM Access Method Services utility.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Cieri, Anthony
Sent: Wednesday, May 20, 2020 1:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
In this instance the IDCAMS command represents a NETVIEW command:
CMDDEF.IDCAMS.MOD=DSIDCAMS
CMDDEF.IDCAMS.FOLDUP=Y
DISPMOD DSIDCAMS
CNM263I MODULE LENGTH CSECTDATE PTF EPA AM ATTR
CNM263I DSIDCAMS 000570 DSIDCAMS 05/30/14 --- 000291B0 24 RN RU
CNM265I END OF DISPLAY
In my example, I am running Netview V6.2.1. I believe that the intent
here was to provide a method for Netview to runs IDCAMS "maintenance" functions
on the various Netview Databases; NLDM, NPDA, TARA etc, without the need to
recycle the Netview tasks. I do use them for such maintenance, but they run
infrequently.
I don't claim to understand the relationship/difference between using
the Netview IDCAMS command and the TSO or batch flavor, but it likely that the
storage issue is related to how Netview invokes IDCAMS.
It might be help to route this question/issue to the Netview users
group. I
Re: Creating new SMS environment in a monoplex
SMSPLEX=SYSPLEX: no, you can't. GDPS K-systems cannot share Dasd with GDPS P-systems, so they must have separate SMS plexes. If you mean: an SMSplex cannot cross Sysplexes: that is true. Kees. -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: 20 May 2020 17:14 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Creating new SMS environment in a monoplex To complement: there is strict requirement to have SMSplex = Sysplex. SMS, as many other system components does support multihost configurations. Multihost could mean several monoplex systems and shared CDS datasets on shared volume. Multihost could also mean SMSplex which covers some sysplex and few monoplexes together. SMSplex could also cover part of sysplex, so different sysplex member may have different SMS settings. As usually IBM recommend to keep SMSplex = sysplex. Note: the above apply to DFSMSrmm, OAM (and tape libraries), etc. However each system component may have it's own specifics/restrictions. AFAIK, in the very old days JES2 MAS could go beyond sysplex. Now it is impossible - JES MAS is available only within sysplex boundaries. However it is possible to have more than one MAS within sysplex. Sometimes sysplex=*plex give some advantages, especially sysplex communication and CF structures. -- Radoslaw Skorupka Lodz, Poland W dniu 19.05.2020 o 21:22, Vernooij, Kees (ITOP NM) - KLM pisze: > I can confirm that. > We have 2 sysplexes (Prod and Test), both with 2 GPDS K-systems. > GDPS K-systems don's share Dasd with the other systems of the sysplex. > So we have 6 SMS environments, each with their own SCDS, ACDS and COMMDS. > We have 1 SMS configuration that covers all systems and in the ACS routines, > we route datasets to storage groups, depending on the system it runs on. > We update the 'source' SMS configuration on the test sysplex systems, > activate it on the 3 SMS environments in the Test Sysplex and test it. > Then we transfer the SCDS to the 3 SMS environments of the Prod Sysplex and > activate it there. > We have no problem with this setup. The advantage is that you don't make > typo's when trying to copy the updates in the test-environment to the > prod-environment. > > Kees. > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Richards, Robert B. > Sent: 19 May 2020 17:58 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Creating new SMS environment in a monoplex > > Thanks, Radoslaw. > > My point, and I think you have also confirmed it, is that an SMS environment > has no specific dependence on a parallel sysplex, CFs, couple datasets, etc. > > All that is left for me is to finish building the system and IPL it. > > Bob > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > R.S. > Sent: Tuesday, May 19, 2020 11:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Creating new SMS environment in a monoplex > > W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze: >> It has been a few decades since I have created a new SMS environment. >> >> Current environment is parallel sysplex replete with CFs and lots of lpars. >> >> I am trying to create a simple SMS environment that will be part of a >> monoplex consisting on one lpar. >> >> I did the following: >> >> >> 1. Defined the new SYSNAME into the base configuration in ISMF and >> activated same. D SMS verified it was defined and not active >> 2. A REPRO of the SCDS into a new SCDS dataset (Alter/newname to >> correct usercat) >> 3. Issued a SETSMS SAVEACDS(also using a SSA connector that I >> subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected >> to a new mastercat) >> 4. Defined an empty COMMDS that I also performed an alter/newname to >> get the desired COMMDS dataset name. >> >> My boss says the ACDS is aware of the original sysplex environment and my >> gyrations of trying to make the above work in a monoplex will not succeed. >> >> Who is right? Will it work or not? > Quick and dirty method: > 1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing > wrong to have non-present system names there. > 2. Copy all *CDS to disk belonging to new system. > 3. IPL the system. > > Of course this is method for some migration. ACS routines, class definitions > and library definitions will be moved. Is that what you want? > Otherwise there is another method, to start from scratch. ACS routines can be > easily imported, class definitions - the only way I know is to re-define them > manually. > BTW: some dummy SMS environment is delivered with ServerPac. I always start > from that point. Then IPL with CPAC system name, then add my name to ACDS > then reIPL with my system name. Then *CDS datasets can be imported (copied). > Piece of cake. > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > == > > Jeśli nie jesteś adresatem tej
Re: REXX assistance
Thanks Tony. I see that IDCAMS used within netview is a valid netview command.
But then I see this in the netview samplib
Define_Base_Cluster_VSAM_File:
/* Called by Define_and_Load_Base_Cluster*/
SAY 'Attempting to define the VSAM file'basename
k.0 = 14
k.1 = ' DEFINE CLUSTER -'
k.2 = ' (NAME ('basename') -'
k.3 = ' INDEXED -'
k.4 = ' KEYS('key_size RKP') -'
k.5 = ' SHAREOPTIONS('shr1 shr2') -'
k.6 = ' RECORDSIZE('avg_recsize max_recsize') -'
k.7 = ' VOLUMES(CPDLB2) -'
k.8 = ' NOREUSE ) -'
k.9 = ' DATA -'
k.10 = ' (NAME ('basename'.DATA) -'
k.11 = ' CYLINDERS('data_size') ) -'
k.12 = ' INDEX -'
k.13 = ' (NAME ('basename'.INDEX) -'
k.14 = ' CYLINDERS('index_size') )'
'PIPE STEM k.|COLLECT|NETV MOE DSIVSMX IDCAMS|STEM R1.'
What purpose is the last line, specifically the NETV MOE DSIVSMX IDCAMS
portion? Why not just NETV MOE IDCAMS?According to the fine manual
DSIVSMX is labelled as a "command processor". Does that imply setting up an
environment? I've asked IBM these questions too.
IBM Tivoli NetView for z/OS, Version 6.2
The DSIVSMX command processor can define, read, and write VSAM keyed files
directly from REXX without using data services tasks. This enables the
implementation of VSAM applications, including end-use application development
in REXX (in conjunction with the pipeline facility), and intensive VSAM
diagnostics.
The DSIVSMX command provides REXX access to keyed VSAM files and to IDCAMS, the
VSAM Access Method Services utility.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Cieri, Anthony
Sent: Wednesday, May 20, 2020 1:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
In this instance the IDCAMS command represents a NETVIEW command:
CMDDEF.IDCAMS.MOD=DSIDCAMS
CMDDEF.IDCAMS.FOLDUP=Y
DISPMOD DSIDCAMS
CNM263I MODULE LENGTH CSECTDATE PTF EPA AM ATTR
CNM263I DSIDCAMS 000570 DSIDCAMS 05/30/14 --- 000291B0 24 RN RU
CNM265I END OF DISPLAY
In my example, I am running Netview V6.2.1. I believe that the intent
here was to provide a method for Netview to runs IDCAMS "maintenance" functions
on the various Netview Databases; NLDM, NPDA, TARA etc, without the need to
recycle the Netview tasks. I do use them for such maintenance, but they run
infrequently.
I don't claim to understand the relationship/difference between using
the Netview IDCAMS command and the TSO or batch flavor, but it likely that the
storage issue is related to how Netview invokes IDCAMS.
It might be help to route this question/issue to the Netview users
group. I believe that they are at Groups.io.
Hth
Tony
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Wednesday, May 20, 2020 12:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
[[ SEI WARNING *** This email was sent from an external source. Do not open
attachments or click on links from unknown or suspicious senders. *** ]]
On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote:
>All,
>...
In a JCL example in
https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_IDCAMS.htm
I see:
//SYSPRINT DD *
Is that probably what the writer intended? Is it even legal?
Writers should hand their examples back to coders for review and testing.
-- gil
--
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
Re: REXX assistance
David, I would, IMHO , check the region= and make sure the main task for Netview and sub tasks. A dump also provide insight into the offending module. I would also check maintenance against Netview. Eileen is correct Profile high is usually TSO rexx , been through this several times. The Rexx internal buffer space is not unlimited, you could ask for another buffer, I.e.; Makebuf equivalent. HTH, Scott On Wed, May 20, 2020 at 1:02 PM Cieri, Anthony < 02d7f4ec1fff-dmarc-requ...@listserv.ua.edu> wrote: > > In this instance the IDCAMS command represents a NETVIEW command: > > CMDDEF.IDCAMS.MOD=DSIDCAMS > CMDDEF.IDCAMS.FOLDUP=Y > > DISPMOD DSIDCAMS > > CNM263I MODULE LENGTH CSECTDATE PTF EPA AM > ATTR > CNM263I DSIDCAMS 000570 DSIDCAMS 05/30/14 --- 000291B0 24 RN > RU > CNM265I END OF DISPLAY > > In my example, I am running Netview V6.2.1. I believe that the > intent here was to provide a method for Netview to runs IDCAMS > "maintenance" functions on the various Netview Databases; NLDM, NPDA, TARA > etc, without the need to recycle the Netview tasks. I do use them for such > maintenance, but they run infrequently. > > I don't claim to understand the relationship/difference between > using the Netview IDCAMS command and the TSO or batch flavor, but it likely > that the storage issue is related to how Netview invokes IDCAMS. > > It might be help to route this question/issue to the Netview users > group. I believe that they are at Groups.io. > > Hth > Tony > > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Paul Gilmartin > Sent: Wednesday, May 20, 2020 12:26 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: REXX assistance > > [[ SEI WARNING *** This email was sent from an external source. Do not > open attachments or click on links from unknown or suspicious senders. *** > ]] > > > On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote: > > >All, > >... > In a JCL example in > > https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_IDCAMS.htm > I see: > //SYSPRINT DD * > > Is that probably what the writer intended? Is it even legal? > Writers should hand their examples back to coders for review and testing. > > -- gil > > -- > 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 > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX assistance
In this instance the IDCAMS command represents a NETVIEW command: CMDDEF.IDCAMS.MOD=DSIDCAMS CMDDEF.IDCAMS.FOLDUP=Y DISPMOD DSIDCAMS CNM263I MODULE LENGTH CSECTDATE PTF EPA AM ATTR CNM263I DSIDCAMS 000570 DSIDCAMS 05/30/14 --- 000291B0 24 RN RU CNM265I END OF DISPLAY In my example, I am running Netview V6.2.1. I believe that the intent here was to provide a method for Netview to runs IDCAMS "maintenance" functions on the various Netview Databases; NLDM, NPDA, TARA etc, without the need to recycle the Netview tasks. I do use them for such maintenance, but they run infrequently. I don't claim to understand the relationship/difference between using the Netview IDCAMS command and the TSO or batch flavor, but it likely that the storage issue is related to how Netview invokes IDCAMS. It might be help to route this question/issue to the Netview users group. I believe that they are at Groups.io. Hth Tony -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Wednesday, May 20, 2020 12:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: REXX assistance [[ SEI WARNING *** This email was sent from an external source. Do not open attachments or click on links from unknown or suspicious senders. *** ]] On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote: >All, >... In a JCL example in https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_IDCAMS.htm I see: //SYSPRINT DD * Is that probably what the writer intended? Is it even legal? Writers should hand their examples back to coders for review and testing. -- gil -- 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: REXX assistance
> I've found no use for ADDRESS LINK/ATTACH. They seem to be
relics of Rexx's gestation under CMS.
I doubt it. It doesn't look like either the CMS tokenized parameter list or the
CMS extended parameter list.
> IIRC, they use R0 as a parameter register.
Passing the address of the ENVBLOCK in R0 is pervasive in REXX. In particular,
REXX also passes the ENVBLOCK in R0 when calling commands in the ATTACHMVS and
LINKMVS environments.
> ADDRESS LINKMVS/ATTCHMVS are similar, but Rexx automatically supplies the
> length prefix.
Prefixes. They seem tailored to calling language processors and utilities,
which include halfword lengths at the beginnings of, e.g., ddname lists.
> Sigh. "IDCAMS" appears to be an implied string literal while context implies
> that "Infile" and "outfile" are Rexx variables.
Bog standard, and perfectly readable, especially if you adopt the convention of
putting the names of uninitialized variables in upper case. I see no value in
novalue.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Wednesday, May 20, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote:
>All,
>
>We have some relatively new Netview automation to process inbound FTP
>processing that is written in REXX,
>
ITschak or Eileen can surely give you better information about
TSO, IDCAMS, and Netview than I. But I know some Rexx.
>Look at how IDCAMS is being called in line 318. ... Is that the equivalent of
>just a standard CALL? Or like entering TSO IDCAMS at a command line in TSO?
>
I believe it's the eqivalent of entering "IDCAMS ..." on the
TSO command line (READY prompt). I believe I've encountered
errors entering such as "TSO IDCAMS ..." as a TSO command.
I find neither TSO nor IDCAMS in the TSO Command Ref.
> ... I see references to LINK, ATTACH, LINKMVS, ATTCHMVS, LINKPGM, ATTCHPGM.
>
I've found no use for ADDRESS LINK/ATTACH. They seem to be
relics of Rexx's gestation under CMS. IIRC, they use R0 as a parameter
register. ADDRESS LINKPGM/ATTCHPGM are similar to their Assembler
macro counterparts. The caller is expected to supply a 16-bit length
prefix if the function called requires it. ADDRESS LINKMVS/ATTCHMVS
are similar, but Rexx automatically supplies the length prefix.
>000309 /* We have now created all the IDCAMS statements, we now write them*/
>000310 /* to our dataset to be used as SYSIN for IDCAMS command */
>000311 /* */
>000312 Say "Number of Queued Lines is " QueuedLines
>000313 Address MVS 'EXECIO 'QueuedLines' DISKW 'Infile' (FINIS'
>000314 /* */
>000315 /* The IDCAMS statement calls IDCAMS using the 2 DD names listed */
>000316 /* after the command as SYSIN and SYSPRINT */
>000317 /* */
>000318 IDCAMS Infile Outfile
>
Sigh. "IDCAMS" appears to be an implied string literal while context implies
that "Infile" and "outfile" are Rexx variables.
The coder could have clarified this enormously with
signal on novalue
SaveTrace = trace( 'R' )
"IDCAMS" Infile Outfile
call trace( SaveTrace )
>000319 Say "IDCAMS RC for File Rename = " RC
>000320 If RC > 4 Then
>000321 Do
>000322 Address MVS 'EXECIO * DISKR 'Outfile' (STEM Prtrex. FINIS'
>000323 do xy = 1 to Prtrex.0
>000324 Say "Idcams output = " Prtrex.xy
>000325 end
>000326 end
>000327 "free fi("Infile")"
>000328 "free fi("Outfile")"
>000329
-- gil
--
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: REXX assistance
On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote: >All, >... In a JCL example in https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zdatamgmt/zsysprogc_utilities_IDCAMS.htm I see: //SYSPRINT DD * Is that probably what the writer intended? Is it even legal? Writers should hand their examples back to coders for review and testing. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX assistance
On Wed, 20 May 2020 06:45:57 -0500, Dave Jousma wrote:
>All,
>
>We have some relatively new Netview automation to process inbound FTP
>processing that is written in REXX,
>
ITschak or Eileen can surely give you better information about
TSO, IDCAMS, and Netview than I. But I know some Rexx.
>Look at how IDCAMS is being called in line 318. ... Is that the equivalent of
>just a standard CALL? Or like entering TSO IDCAMS at a command line in TSO?
>
I believe it's the eqivalent of entering "IDCAMS ..." on the
TSO command line (READY prompt). I believe I've encountered
errors entering such as "TSO IDCAMS ..." as a TSO command.
I find neither TSO nor IDCAMS in the TSO Command Ref.
> ... I see references to LINK, ATTACH, LINKMVS, ATTCHMVS, LINKPGM, ATTCHPGM.
>
>
I've found no use for ADDRESS LINK/ATTACH. They seem to be
relics of Rexx's gestation under CMS. IIRC, they use R0 as a parameter
register. ADDRESS LINKPGM/ATTCHPGM are similar to their Assembler
macro counterparts. The caller is expected to supply a 16-bit length
prefix if the function called requires it. ADDRESS LINKMVS/ATTCHMVS
are similar, but Rexx automatically supplies the length prefix.
>000309 /* We have now created all the IDCAMS statements, we now write them*/
>000310 /* to our dataset to be used as SYSIN for IDCAMS command */
>000311 /* */
>000312 Say "Number of Queued Lines is " QueuedLines
>000313 Address MVS 'EXECIO 'QueuedLines' DISKW 'Infile' (FINIS'
>000314 /* */
>000315 /* The IDCAMS statement calls IDCAMS using the 2 DD names listed */
>000316 /* after the command as SYSIN and SYSPRINT */
>000317 /* */
>000318 IDCAMS Infile Outfile
>
Sigh. "IDCAMS" appears to be an implied string literal while context implies
that "Infile" and "outfile" are Rexx variables.
The coder could have clarified this enormously with
signal on novalue
SaveTrace = trace( 'R' )
"IDCAMS" Infile Outfile
call trace( SaveTrace )
>000319 Say "IDCAMS RC for File Rename = " RC
>000320 If RC > 4 Then
>000321 Do
>000322 Address MVS 'EXECIO * DISKR 'Outfile' (STEM Prtrex. FINIS'
>000323 do xy = 1 to Prtrex.0
>000324 Say "Idcams output = " Prtrex.xy
>000325 end
>000326 end
>000327 "free fi("Infile")"
>000328 "free fi("Outfile")"
>000329
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IODF Activation Question
for some reason I didn't see the original post, I have a similar issue, for the first time, removing some devices, I've been successful when I hard activate the new IODF from one system on the CEC, all others should be OK with a soft activation. saying that, I still have an out of sync condition myself due to control units and devices being removed, I see my only alternative is to POR :( so ACTIVATE IODF=00 on one LPAR in the COMPLEX (FORCE POSSIBLY) then ACTIVATE IODF=00,SOFT on all the others Carmen Vitullo - Original Message - From: "David Jousma" <01a0403c5dc1-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, May 20, 2020 9:59:47 AM Subject: Re: IODF Activation Question What cannot be done dynamically? If not dynamic, then it sounds like a POR? _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Wednesday, May 20, 2020 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IODF Activation Question **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** We have 8 systems in a sysplex that share a single IODF dataset, all dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD changes that can't be dynamically activated, each system will need to be IPLed with the new IODF. Once I do so however, the hardware and software IODF will be out of sync. How do I get them back in sync? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://protect2.fireeye.com/url?k=8ff4d39f-d3a82790-8ff4f907-0cc47a33347c-4e8b6fa59ed3960b=https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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: Creating new SMS environment in a monoplex
To complement: there is strict requirement to have SMSplex = Sysplex. SMS, as many other system components does support multihost configurations. Multihost could mean several monoplex systems and shared CDS datasets on shared volume. Multihost could also mean SMSplex which covers some sysplex and few monoplexes together. SMSplex could also cover part of sysplex, so different sysplex member may have different SMS settings. As usually IBM recommend to keep SMSplex = sysplex. Note: the above apply to DFSMSrmm, OAM (and tape libraries), etc. However each system component may have it's own specifics/restrictions. AFAIK, in the very old days JES2 MAS could go beyond sysplex. Now it is impossible - JES MAS is available only within sysplex boundaries. However it is possible to have more than one MAS within sysplex. Sometimes sysplex=*plex give some advantages, especially sysplex communication and CF structures. -- Radoslaw Skorupka Lodz, Poland W dniu 19.05.2020 o 21:22, Vernooij, Kees (ITOP NM) - KLM pisze: I can confirm that. We have 2 sysplexes (Prod and Test), both with 2 GPDS K-systems. GDPS K-systems don's share Dasd with the other systems of the sysplex. So we have 6 SMS environments, each with their own SCDS, ACDS and COMMDS. We have 1 SMS configuration that covers all systems and in the ACS routines, we route datasets to storage groups, depending on the system it runs on. We update the 'source' SMS configuration on the test sysplex systems, activate it on the 3 SMS environments in the Test Sysplex and test it. Then we transfer the SCDS to the 3 SMS environments of the Prod Sysplex and activate it there. We have no problem with this setup. The advantage is that you don't make typo's when trying to copy the updates in the test-environment to the prod-environment. Kees. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Richards, Robert B. Sent: 19 May 2020 17:58 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Creating new SMS environment in a monoplex Thanks, Radoslaw. My point, and I think you have also confirmed it, is that an SMS environment has no specific dependence on a parallel sysplex, CFs, couple datasets, etc. All that is left for me is to finish building the system and IPL it. Bob -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: Tuesday, May 19, 2020 11:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Creating new SMS environment in a monoplex W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze: It has been a few decades since I have created a new SMS environment. Current environment is parallel sysplex replete with CFs and lots of lpars. I am trying to create a simple SMS environment that will be part of a monoplex consisting on one lpar. I did the following: 1. Defined the new SYSNAME into the base configuration in ISMF and activated same. D SMS verified it was defined and not active 2. A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct usercat) 3. Issued a SETSMS SAVEACDS(also using a SSA connector that I subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected to a new mastercat) 4. Defined an empty COMMDS that I also performed an alter/newname to get the desired COMMDS dataset name. My boss says the ACDS is aware of the original sysplex environment and my gyrations of trying to make the above work in a monoplex will not succeed. Who is right? Will it work or not? Quick and dirty method: 1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing wrong to have non-present system names there. 2. Copy all *CDS to disk belonging to new system. 3. IPL the system. Of course this is method for some migration. ACS routines, class definitions and library definitions will be moved. Is that what you want? Otherwise there is another method, to start from scratch. ACS routines can be easily imported, class definitions - the only way I know is to re-define them manually. BTW: some dummy SMS environment is delivered with ServerPac. I always start from that point. Then IPL with CPAC system name, then add my name to ACDS then reIPL with my system name. Then *CDS datasets can be imported (copied). Piece of cake. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy
Re: IODF Activation Question
One CEC, 8 systems in a sysplex, (plus others on the same CEC, not important for this exercise). Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 11:09 AM, Mazer Ken G <01e8b07bfbbe-dmarc-requ...@listserv.ua.edu> wrote: > Mark, > > You've indicated that you have 8 systems in a sysplex does that mean 8 CEC or > 8 z/OS systems? > How many CEC's do you have? > Are you doing POR for each CEC? > In the RESET profile you point to the IOCDS slot that you'll POR from. In > SYS1.IPLPARM(LOADxx) you should specify "**" in columns 10 & 11. This will > cause the latest POR activated IODF to be read. > Word of caution, if you don't share DASD between each of the systems, make > sure you have the same IODF accessible to each system. You may need to DUMP, > FTP, RESTORE to get it to the other systems. > > If you can dynamically activate, you'll want to do software activates on all > but one LPAR, this is where you'll want to do a hardware activate. > If you're unable to do a dynamic hardware activate then it's POR time. > > Hope this helps. > > Ken Mazer > > -Original Message- > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Wednesday, May 20, 2020 10:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IODF Activation Question > > We have 8 systems in a sysplex that share a single IODF dataset, all dynamic > IODF activation's occur in this sysplex. I'm looking to perform HCD changes > that can't be dynamically activated, each system will need to be IPLed with > the new IODF. Once I do so however, the hardware and software IODF will be > out of sync. How do I get them back in sync? > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > --- > > 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: IODF Activation Question
The hardware and software tokens are currently in sync. If I'm able to update just the hardware piece of the new IODF, I can IPL each of the systems using the new IODF, and get them back in sync again. I just don't know if that's possible, i.e. just do the hardware piece. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 11:05 AM, Edgington, Jerry wrote: > If you have hardware in sync, but the software. Then you should be able to a > software only activate on the LPAR, to bring them back in sync. For hardware > sync, you would need the IOCDS hardware token to match the IODF. > > -Original Message- > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Jousma, David > Sent: Wednesday, May 20, 2020 11:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: IODF Activation Question > > This message was sent from an external source outside of Western & Southern's > network. Do not click links or open attachments unless you recognize the > sender and know the contents are safe. > > What cannot be done dynamically? If not dynamic, then it sounds like a POR? > > Dave Jousma > AVP | Manager, Systems Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, > MI 49546 > 616.653.8429 | fax: 616.653.2717 > > -Original Message- > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Wednesday, May 20, 2020 10:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IODF Activation Question > > CAUTION EXTERNAL EMAIL > > DO NOT open attachments or click on links from unknown senders or unexpected > emails > > We have 8 systems in a sysplex that share a single IODF dataset, all dynamic > IODF activation's occur in this sysplex. I'm looking to perform HCD changes > that can't be dynamically activated, each system will need to be IPLed with > the new IODF. Once I do so however, the hardware and software IODF will be > out of sync. How do I get them back in sync? > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://protect2.fireeye.com/url?k=8ff4d39f-d3a82790-8ff4f907-0cc47a33347c-4e8b6fa59ed3960b=https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN CAUTION EXTERNAL > EMAIL > > DO NOT open attachments or click on links from unknown senders or unexpected > emails > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message was > misdirected. After replying, please erase it from your computer system. Your > assistance in correcting this error is appreciated. > > > - > > For IBM-MAIN subscribe / signoff / archive access instructions,
Re: IODF Activation Question
You can use Novalidate command to activate dynamically. /ACTIVATE IODF,=xx,SOFT=NOVALIDATE note :xx is your 2 charecter of IODF file. On Wed, May 20, 2020, 8:23 PM Mark Jacobs < 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > We have 8 systems in a sysplex that share a single IODF dataset, all > dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD > changes that can't be dynamically activated, each system will need to be > IPLed with the new IODF. Once I do so however, the hardware and software > IODF will be out of sync. How do I get them back in sync? > > Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted > email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > -- > 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: IODF Activation Question
Mark, You've indicated that you have 8 systems in a sysplex does that mean 8 CEC or 8 z/OS systems? How many CEC's do you have? Are you doing POR for each CEC? In the RESET profile you point to the IOCDS slot that you'll POR from. In SYS1.IPLPARM(LOADxx) you should specify "**" in columns 10 & 11. This will cause the latest POR activated IODF to be read. Word of caution, if you don't share DASD between each of the systems, make sure you have the same IODF accessible to each system. You may need to DUMP, FTP, RESTORE to get it to the other systems. If you can dynamically activate, you'll want to do software activates on all but one LPAR, this is where you'll want to do a hardware activate. If you're unable to do a dynamic hardware activate then it's POR time. Hope this helps. Ken Mazer -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Wednesday, May 20, 2020 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IODF Activation Question We have 8 systems in a sysplex that share a single IODF dataset, all dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD changes that can't be dynamically activated, each system will need to be IPLed with the new IODF. Once I do so however, the hardware and software IODF will be out of sync. How do I get them back in sync? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- 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: IODF Activation Question
I'm trying to move several hundred UCBs to 31 bit storage. It can't be done dynamically since those devices are online to those systems. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 10:59 AM, Jousma, David <01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > What cannot be done dynamically? If not dynamic, then it sounds like a POR? > > Dave Jousma > AVP | Manager, Systems Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, > MI 49546 > 616.653.8429 | fax: 616.653.2717 > > -Original Message- > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Mark Jacobs > > Sent: Wednesday, May 20, 2020 10:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IODF Activation Question > > CAUTION EXTERNAL EMAIL > > DO NOT open attachments or click on links from unknown senders or unexpected > emails > > We have 8 systems in a sysplex that share a single IODF dataset, all dynamic > IODF activation's occur in this sysplex. I'm looking to perform HCD changes > that can't be dynamically activated, each system will need to be IPLed with > the new IODF. Once I do so however, the hardware and software IODF will be > out of sync. How do I get them back in sync? > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://protect2.fireeye.com/url?k=8ff4d39f-d3a82790-8ff4f907-0cc47a33347c-4e8b6fa59ed3960b=https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN CAUTION EXTERNAL > EMAIL > > DO NOT open attachments or click on links from unknown senders or unexpected > emails > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message was > misdirected. After replying, please erase it from your computer system. Your > assistance in correcting this error is appreciated. > > > - > > 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: IODF Activation Question
If you have hardware in sync, but the software. Then you should be able to a software only activate on the LPAR, to bring them back in sync. For hardware sync, you would need the IOCDS hardware token to match the IODF. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jousma, David Sent: Wednesday, May 20, 2020 11:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IODF Activation Question This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. What cannot be done dynamically? If not dynamic, then it sounds like a POR? _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Wednesday, May 20, 2020 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IODF Activation Question **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** We have 8 systems in a sysplex that share a single IODF dataset, all dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD changes that can't be dynamically activated, each system will need to be IPLed with the new IODF. Once I do so however, the hardware and software IODF will be out of sync. How do I get them back in sync? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://protect2.fireeye.com/url?k=8ff4d39f-d3a82790-8ff4f907-0cc47a33347c-4e8b6fa59ed3960b=https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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: IODF Activation Question
What cannot be done dynamically? If not dynamic, then it sounds like a POR? _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Wednesday, May 20, 2020 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IODF Activation Question **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** We have 8 systems in a sysplex that share a single IODF dataset, all dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD changes that can't be dynamically activated, each system will need to be IPLed with the new IODF. Once I do so however, the hardware and software IODF will be out of sync. How do I get them back in sync? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://protect2.fireeye.com/url?k=8ff4d39f-d3a82790-8ff4f907-0cc47a33347c-4e8b6fa59ed3960b=https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IODF Activation Question
We have 8 systems in a sysplex that share a single IODF dataset, all dynamic IODF activation's occur in this sysplex. I'm looking to perform HCD changes that can't be dynamically activated, each system will need to be IPLed with the new IODF. Once I do so however, the hardware and software IODF will be out of sync. How do I get them back in sync? Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX assistance
Is not PROF for TSO, not Netview? The 878 abend is occurring in Netview.
You can just use Netview to automate the starting of a procedure to run
directly under TSO.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
ITschak Mugzach
Sent: Wednesday, May 20, 2020 8:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX assistance
It's simple. use "PROF VARSTORAGE(HIGH)" to direct EXECIO and other getmains
above the line.
ITschak
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring for
z/OS, x/Linux & IBM I **| z/VM comming son *
On Wed, May 20, 2020 at 2:46 PM Dave Jousma <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
> All,
>
> We have some relatively new Netview automation to process inbound FTP
> processing that is written in REXX, and over time we’ve seen Netview abends
> with 878’s, etc. IBM indicates we may have a problem below the line,
> specifically SP0 being exhausted. They are seeing a lot junk that looks
> like workpack volser’s PCW, temp dataset names, etc. It is my belief
> that it is the remnants of calling IDCAMS to do our FTP processing to
> create special dataset catalog entries amongst other stuff and cleanup
> is not occurring that over time causes our problems.
>
> Here is the bit of rexx code I am looking at. Look at how IDCAMS is
> being called in line 318. I’m not a REXX coding expert by any means.
> Is that the equivalent of just a standard CALL? Or like entering TSO
> IDCAMS at a command line in TSO? I’m wondering if there is a better way to
> call
> IDCAMS? I see references to LINK, ATTACH, LINKMVS, ATTCHMVS, LINKPGM,
> ATTCHPGM. I’m embarrassed to say that I do not know the nuances of each of
> these, and when appropriate to use. Do any of these create a new
> environment, do the function, and then tear the environment down upon
> exit? It seems like this is what we need to use to fix this issue.
>
> 000308 /*
> */
> 000309 /* We have now created all the IDCAMS statements, we now write
> them*/
> 000310 /* to our dataset to be used as SYSIN for IDCAMS command */
> 000311 /*
> */
> 000312 Say "Number of Queued Lines is " QueuedLines
>
> 000313 Address MVS 'EXECIO 'QueuedLines' DISKW 'Infile' (FINIS'
>
> 000314 /*
> */
> 000315 /* The IDCAMS statement calls IDCAMS using the 2 DD names
> listed */
> 000316 /* after the command as SYSIN and SYSPRINT */
> 000317 /*
> */
> 000318 IDCAMS Infile Outfile
>
> 000319 Say "IDCAMS RC for File Rename = " RC
>
> 000320 If RC > 4 Then
>
> 000321 Do
>
> 000322 Address MVS 'EXECIO * DISKR 'Outfile' (STEM Prtrex.
> FINIS'
> 000323 do xy = 1 to Prtrex.0
>
> 000324 Say "Idcams output = " Prtrex.xy
>
> 000325 end
>
> 000326 end
>
> 000327 "free fi("Infile")"
>
> 000328 "free fi("Outfile")"
>
> 000329
>
>
> --
> 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
This e-mail, including any attachments, may be confidential, privileged or
otherwise legally protected. It is intended only for the addressee. If you
received this e-mail in error or from someone who was not authorized to send it
to you, do not disseminate, copy or otherwise use this e-mail or its
attachments. Please notify the sender immediately by reply e-mail and delete
the e-mail from your system.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: REXX assistance
It's simple. use "PROF VARSTORAGE(HIGH)" to direct EXECIO and other
getmains above the line.
ITschak
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM comming son *
On Wed, May 20, 2020 at 2:46 PM Dave Jousma <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
> All,
>
> We have some relatively new Netview automation to process inbound FTP
> processing that is written in REXX, and over time we’ve seen Netview abends
> with 878’s, etc. IBM indicates we may have a problem below the line,
> specifically SP0 being exhausted. They are seeing a lot junk that looks
> like workpack volser’s PCW, temp dataset names, etc. It is my belief
> that it is the remnants of calling IDCAMS to do our FTP processing to
> create special dataset catalog entries amongst other stuff and cleanup is
> not occurring that over time causes our problems.
>
> Here is the bit of rexx code I am looking at. Look at how IDCAMS is
> being called in line 318. I’m not a REXX coding expert by any means. Is
> that the equivalent of just a standard CALL? Or like entering TSO IDCAMS at
> a command line in TSO? I’m wondering if there is a better way to call
> IDCAMS? I see references to LINK, ATTACH, LINKMVS, ATTCHMVS, LINKPGM,
> ATTCHPGM. I’m embarrassed to say that I do not know the nuances of each of
> these, and when appropriate to use. Do any of these create a new
> environment, do the function, and then tear the environment down upon
> exit? It seems like this is what we need to use to fix this issue.
>
> 000308 /*
> */
> 000309 /* We have now created all the IDCAMS statements, we now write
> them*/
> 000310 /* to our dataset to be used as SYSIN for IDCAMS command
> */
> 000311 /*
> */
> 000312 Say "Number of Queued Lines is " QueuedLines
>
> 000313 Address MVS 'EXECIO 'QueuedLines' DISKW 'Infile' (FINIS'
>
> 000314 /*
> */
> 000315 /* The IDCAMS statement calls IDCAMS using the 2 DD names listed
> */
> 000316 /* after the command as SYSIN and SYSPRINT
> */
> 000317 /*
> */
> 000318 IDCAMS Infile Outfile
>
> 000319 Say "IDCAMS RC for File Rename = " RC
>
> 000320 If RC > 4 Then
>
> 000321 Do
>
> 000322 Address MVS 'EXECIO * DISKR 'Outfile' (STEM Prtrex.
> FINIS'
> 000323 do xy = 1 to Prtrex.0
>
> 000324 Say "Idcams output = " Prtrex.xy
>
> 000325 end
>
> 000326 end
>
> 000327 "free fi("Infile")"
>
> 000328 "free fi("Outfile")"
>
> 000329
>
>
> --
> 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
REXX assistance
All,
We have some relatively new Netview automation to process inbound FTP
processing that is written in REXX, and over time we’ve seen Netview abends
with 878’s, etc. IBM indicates we may have a problem below the line,
specifically SP0 being exhausted. They are seeing a lot junk that looks like
workpack volser’s PCW, temp dataset names, etc. It is my belief that it
is the remnants of calling IDCAMS to do our FTP processing to create special
dataset catalog entries amongst other stuff and cleanup is not occurring that
over time causes our problems.
Here is the bit of rexx code I am looking at. Look at how IDCAMS is being
called in line 318. I’m not a REXX coding expert by any means. Is that the
equivalent of just a standard CALL? Or like entering TSO IDCAMS at a command
line in TSO? I’m wondering if there is a better way to call IDCAMS? I see
references to LINK, ATTACH, LINKMVS, ATTCHMVS, LINKPGM, ATTCHPGM. I’m
embarrassed to say that I do not know the nuances of each of these, and when
appropriate to use. Do any of these create a new environment, do the
function, and then tear the environment down upon exit? It seems like this is
what we need to use to fix this issue.
000308 /* */
000309 /* We have now created all the IDCAMS statements, we now write them*/
000310 /* to our dataset to be used as SYSIN for IDCAMS command */
000311 /* */
000312 Say "Number of Queued Lines is " QueuedLines
000313 Address MVS 'EXECIO 'QueuedLines' DISKW 'Infile' (FINIS'
000314 /* */
000315 /* The IDCAMS statement calls IDCAMS using the 2 DD names listed */
000316 /* after the command as SYSIN and SYSPRINT */
000317 /* */
000318 IDCAMS Infile Outfile
000319 Say "IDCAMS RC for File Rename = " RC
000320 If RC > 4 Then
000321 Do
000322 Address MVS 'EXECIO * DISKR 'Outfile' (STEM Prtrex. FINIS'
000323 do xy = 1 to Prtrex.0
000324 Say "Idcams output = " Prtrex.xy
000325 end
000326 end
000327 "free fi("Infile")"
000328 "free fi("Outfile")"
000329
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
