Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Nolan

Pages: 1 [2] 3 4 5 6 7 ... 10
16
Pretty close to the same as yours.

Code: [Select]
OUTCLASS(A-Z) BLNKTRNC=YES,       /* Blank Trunc'n for non-page ds   */   
         OUTDISP=(WRITE,          /* outdisp for normal termination  */   
                  WRITE),         /* and for abnormal termination    */   
         OUTPUT=PRINT,            /* print class                     */   
         TRKCELL=YES              /* use track celling               */   

17
We run many instances of ARSYSPIN on the same system.   We use different classes pointing to different Applications.  In our test system we have 7 different instances of ARSYSPIN running reading different destinations and classes.  We don't use the SELFORM option but I doubt it would be a problem.

Here is a snippet of 3 of our prod ARSYSPINs that have been running for years with no problem.

Local class A ARSYSPIN sysin
APPL="JOBLOGA-VAR"       
APPLGROUP="JOBLOG-MONTH6"
JESCLASS=A               
SELDEST=LOCAL

Local class 0 ARSYSPIN sysin
APPL="JOBLOG0-VAR"         
APPLGROUP="JOBLOG-MONTH6" 
JESCLASS=0                 
SELDEST=LOCAL

Remote DEST RMT5000 classes 01ADGJRU ARSYSPIN sysin
APPL="JOBLOG2-VAR"       
APPLGROUP="JOBLOG-MONTH1"
JESCLASS=01ADGJRU     
SELDEST=RMT5000         

You should have no problems but as we always say, try it in DEV  :).

18
z/OS Server / Re: JES Extractor
« on: July 25, 2019, 04:46:31 AM »
If you are running CMOD on Z/OS, then you might be looking for the ARSYSPIN which is included with the base CMOD server.
https://www.ibm.com/support/knowledgecenter/en/SSQHWE_9.5.0/com.ibm.ondemand.administeringzos.doc/doday000.htm

If you are running CMOD on a different platform then I believe a 3rd party company will sell you a tool to perform JES2 extractions and push down to your distributed CMOD.

19
z/OS Server / Re: Convert AFP to XML
« on: July 17, 2019, 11:01:04 AM »
IBM CMOD is staying out of the transformation business, CMOD does not have AFP to XML built-in that I am aware of.   Check with Crawfordtech tools, they offer all kinds of transforms.

20
z/OS Server / Re: Getting content out of CMOD z/OS
« on: June 21, 2019, 10:52:29 AM »
Sounds absolutely crazy but I know there are a lot of people smarter than me.   The OAM objects are only related from tables in OnDemand, the compression used on each report can be different.   If it was possible, then IBM would have delivered a more integrated connection to Records Manager.   I don't think I have ever heard IBM or an external supplier claim that it can be done.   Any migration always involves extracting the data using OnDemand tools and then sending it to a different platform.    If the engineers can prove they can rebuild one compressed OAM report without breaking any licensing agreements with IBM.  Let us know. 

My guess -1 :)

21
z/OS Server / Re: CMOD 10.1 and 64Bi functions
« on: June 19, 2019, 10:03:21 AM »
We are using the arsusec out of the box with ARSUSECX.   Do you think that would be the root cause of ODF running slow when we throw out 1400 distributions at once?

22
z/OS Server / Re: CMOD 10.1 and 64Bi functions
« on: June 10, 2019, 02:34:56 PM »
So far I have not needed to do anything in 64bit.   However, our banner exit for ODF is a problem and I haven't had a chance to dig deep to find out why but it messes up ODF and uses 35% more CPU.   I will update if I do stumble across anything that does require 64 bit.

Cheers

23
z/OS Server / Re: ODF Banner Exit performance on V10.1
« on: May 16, 2019, 10:37:01 AM »
Using the exact options provided by IBM.  I don't believe there is much we can change for the banner exit.

//COBOL2  EXEC PGM=IGYCRCTL,REGION=0M,PARM='DLL,LIST,MAP,OBJ,RENT,
//             TRUNC(OPT),NOSEQ,XREF,EXP,THREAD,PGMN(LM)'         


//LKED     EXEC PGM=IEWL,COND=(4,LT),                   
//     PARM='CASE=MIXED,COMPAT=ZOSV1R11,OPTIONS=OPTS'   
...
//OPTS     DD  *                                         
    XREF                                                 
    AMODE=31,MAP                                         
    RENT,DYNAM(DLL)                                     

24
z/OS Server / ODF Banner Exit performance on V10.1
« on: May 16, 2019, 09:25:27 AM »
Good day,

We have upgraded to V10.1 from V9.5 in our test system and have found an almost 35% increase in processing time when using our banner Exit.  There were no changes to the exit between V9.5 and V10.1, we recompiled using the new modules and see a drastic impact on throughput.   Anyone else had a similar experience?

It is not a complex banner exit, we read the customer vars for some flags, convert some text to big letters, and push out Dist address info/Dist ID/Report ID/Jobname.


25
z/OS Server / Re: CMOD & JES3 local
« on: March 07, 2019, 06:56:52 AM »
CMOD runs on Z/OS,  not sure I understand the question.  Are you asking if the arsload and arsyspin can pull from a JES3 spool?

26
z/OS Server / Re: ODF justification
« on: February 22, 2019, 10:18:57 AM »
We use ODF on Z/OS not sure how it works on distributed.   Here are two cool things we do that are a little different, there could be better ways but this was set up years ago.

- We create ODF bundle distributions and send the results back to OnDemand for ingestion.  This allows us to have repacked reports for viewing, exporting.
- We also combine the banner exit, Automation (AOC), to flag when a report is successfully archived.  A dummy distribution kicks off and the banner exit puts out a WTO for the automation to capture a message and then post a flag in our scheduler.  This is required for reports that are loaded via the spool and you don't know when it successfully archived.

 

27
You need to download the data from Z/OS in binary format.  Then you can use the wizard to setup indexing.  The other way is not to use the wizard but do it manually which is what we do normally.  Don't use anything ANSI if it is for Z/OS EBCIDIC.

28
z/OS Server / Re: ARSYSPIN user exits
« on: January 30, 2019, 02:34:23 PM »
Sorry, only have 01 and 06 deployed for ARSYSPIN.  It is in assembler so I struggle whenever I need to look at it!

29
z/OS Server / Re: Primary Storage node definition
« on: January 23, 2019, 11:44:51 AM »
You can't have two for the same application. 
If you are set on adding a new storage node,
- You will need to then create new AGs to point to the storage node
- New applications to point to the new ag
- Update your folders to have the old and new ags mapped correctly
- All the CRT rows that have the old ags and app names would need to be updated.

Then it would flow to the new Storage Node for all new archives.    We have over 4000 collection names in our main storage node and don't have any problems.  Not sure why you need a new storage node unless you are changing the media (OAM,TSM,Cache)

If you are set up using the Report Specification Exit, you can update the collection names and add the new names to the existing storage node.  The CRT table is only read during the report specification exit not at retrieval.  We have done this for cases where we needed to change retention on a particular report.

Hopefully, the latter suggestion is what you are looking for.

30
z/OS Server / Re: Primary Storage node definition
« on: January 23, 2019, 10:45:26 AM »
If you have a CRT table, are you not using the report specification exit to set the collection name?  By updating the CRT table and adding the new collection name to the existing storage node you should be able to have many different collection names used and only one storage node.  We have one storage node and 1000s of collection names with different oam groups.

Not sure what ZORP is so maybe my response is not helpful.

Pages: 1 [2] 3 4 5 6 7 ... 10