Thanks John.  I appreciate it.  We are working a PMR with IBM Netview support.  
We're going to run a getmain/freemain trace specifically of SP0 below the line 
to see if we can see a pattern.   We've been somewhat "guessing" at the culprit 
based on the eye catchers we see in that subpool from the dumps.   

Your suggestion is good.  I also have asked IBM, but have gotten no response 
yet about the difference in syntax calling IDCAMS like this:

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                                


Or from this Netview Sample.  I get the entire PIPE portion of all this, but my 
question is specifically calling idcams as NETV MOE DSIVSMX IDCAMS

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.'   
 Define_rc = 4;                                            

_____________________________________________________________________________________________________
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 
John S. Giltner, Jr.
Sent: Friday, May 22, 2020 9:09 AM
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**

As others have pointed out "IDCAMS" is a NetView command that calls IDCAMS.  
The original intent was to allow you to automate maintenance of  the VSAM files 
that NetView uses without bringing down NetView.  However I sure that others, 
like you and me, have found other purposes for it.

We also use it for inbound file transfer automation to rename the files so they 
have date/time stamps.  I have never experienced 878 abends, but that could be 
due to the number of times it is called.  We now have FTP exits that add the 
date/time stamps when the file is created the majority of the time  instead of 
after the transfer ends.   So end up not doing renames calling IDCAMS that much.

From NetView I don't know of another way to call IDCAMS, the only thing I can 
think of would be to change your automation so that instead of calling IDCAMS 
directly from NetView is to create a file with the control statements you need 
and then submit either a batch job or run it as a separate started task 
pointing to the file with the control statements.  I think somebody else 
suggested this also.

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

Reply via email to