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 ... 10
1
z/OS Server / Re: 10.1 Release Notes
« on: April 28, 2020, 07:33:48 AM »
Adding to the stricter rules. 

Comments must be /* comment */   - No space between forward slash and the asterisk.

The error message was
ARS5481I INDEX1='SEC_ID',FIELD1,(TYPE=GROUP,BREAK=YES)                / *SEC ID */
ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR BREAK


The issue was the comment!!!   


2
z/OS Server / Re: Return Code from OnDemand
« on: February 07, 2020, 02:16:39 PM »
Then it is not possible to capture the OnDemand success or failure error code in JCL.  I recommend for any critical loading you use arsload via the batch JCL method, any failures will provide a non zero return code.

3
z/OS Server / Re: Return Code from OnDemand
« on: February 07, 2020, 01:58:50 PM »
It sounds like you are dumping the file to the spool versus using the arsload in the JCL.  If you have arsload in the JCL and it still is not giving you are return code, let us know the parms on the arsload statement in the JCL and what version of OnDemand you are running.

4
z/OS Server / Re: 10.1 Release Notes
« on: January 30, 2020, 10:10:12 AM »
Adding to Indexer parm tightened up for NODX

If you see this:

ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR NAME

Then the solution is to change

INDEX03=PAGE_NO,FIELD1,(TYPE=GROUPRANGE)

to

INDEX03='PAGE_NO',FIELD1,(TYPE=GROUPRANGE)

Quotes are now enforced on the index name.

We found all of ours to clean up using this query.

select name  from $DBOWNER$.arsapp
where indexer like '%INDEXSTYLE=NODX%' and indexer like '%INDEX%=P%'

5
z/OS Server / Re: CMOD 9.5 to 10.1 when 10.1 is already running
« on: January 06, 2020, 08:12:24 AM »
Your response is still very unclear on what you are trying to accomplish.  The server and the client are to different parts and can run at different levels. (see compatibility matrix)

What you need to do is upgrade your servers to 10.1.x in all locations to be running a fully supported product.

For the thick client, you can roll out the updated version 10.1.x to your user base before or after the server is upgraded.
If you have users using ICN, then that server should also get the updated OnDemand server binaries installed for ODWEK.

6
z/OS Server / ODSSGET in Anystore Exit stuck on first DDNAME
« on: October 28, 2019, 08:16:48 AM »
Hello folks, we have upgraded our test system to 10.1.0.4 and in testing the Anystore exit via ARSLOAD it fails on a 2nd file being processed.  The ODSSGET module is stuck pointing to the EOF of the inital DDNAME loaded.

@rjchavez said years ago

"The ODSSGET routine is called to OPEN, READ, and CLOSE files including the actual report files.  These traditional MVS services were causing the issue (still not sure why).  I changed the exit to use FOPEN, FREAD, and FCLOSE instead.  This corrected the problem."  - http://www.odusergroup.org/forums/index.php?topic=1777.0

I don't have any documentation on ODSSGET as like others, Lab Services provided it without source code. :(

Q1. FOPEN/FREAD/FCLOSE?  Is that part of ODSSGET or something written in C?
Q2. Does anyone know how to reset the ODSSGET (initialize it).  I have tried ODSSGET-CLOSE and ODSSGET-OPEN but the results are the same.  Remains pointing to the EOF on initial DDNAME.

Initial Load
Init Call ODSSGET           
Set ODSSGET-OPEN to True
ODSSGET-DDNAME     :SYS00001
ODSSGET-RETURN-CODE:00000   
ODSSGET-REASON-CODE:00000   
ODSSGET-DDNAME     :SYS00001
ODSSGET-ACTION     :OPEN   
...
Terminate Anyssotre Exit with ODSSGET-CLOSE
Set ODSSGET-CLOSE to True
Perform CALL-ODSSGET.   
ODSSGET-DDNAME     :SYS00001
ODSSGET-RETURN-CODE:00001   
ODSSGET-REASON-CODE:01001   
...
2nd file
Init Call ODSSGET             
Set ODSSGET-OPEN to True
CEE3201S The system detected an operation exception (System Completion Code=0C1)


Any suggestions are welcome.

Thanks




7
z/OS Server / Re: Loads Failing
« on: October 07, 2019, 11:21:07 AM »
Check the Z/OS logs at load time for an SMS message explaining why it doesn't like the collection name.   Was there any change to SMS routines over the weekend?  You sure your report specification exit is putting the correct APP/AG and collection node to use?

You should also move to a new version of OnDemand to get IBM support. :)


8
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               */   

9
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  :).

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

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

12
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 :)

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

14
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

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

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