Messages

451

z/OS Server / Re: Can't get a trace file written

« on: July 23, 2018, 07:41:51 AM »

A colleague had this write up which I think is still accurate:

https://www.ibm.com/developerworks/community/blogs/e8206aad-10e2-4c49-b00c-fee572815374/entry/cmod_trace?lang=en

There's also the -1 and -2 trace parms - am curious as to why you're not using those?

Ed

452

z/OS Server / Re: z/OS V2.3 Release Notes

« on: July 19, 2018, 07:01:29 AM »

More recommended maintenance:

After applying z/OS maintenance I can no longer retrieve OnDemand V2 migrated documents.

http://www-01.ibm.com/support/docview.wss?uid=swg22008017

Ed

453

z/OS Server / Re: z/OS V2.3 Release Notes

« on: July 17, 2018, 01:29:06 PM »

Looks like you're picking up a default.

Ed

454

Tips and Tricks / Re: JCL That I Find Handy

« on: July 13, 2018, 07:54:12 AM »

When using a //DD:PARM if it's not working for you, put each parm on a separate line.

Ref:

https://www.ibm.com/support/knowledgecenter/en/SSQHWE_9.5.0/com.ibm.ondemand.administeringzos.doc/dodal002.htm

//STEP1    EXEC PGM=ARSLOAD,REGION=0M,
// PARM=('/-V //DD:PARM -u odadmin -p passwd')
//STEPLIB  DD DSN=ARS.V9R5M0.SARSLOAD,DISP=SHR
//         DD DSN=DB2.V10R1M0.SDSNEXIT,DISP=SHR 
//         DD DSN=DB2.V10R1M0.SDSNLOAD,DISP=SHR 
//         DD DSN=ACIF.V2R3M1.SAPKMOD1,DISP=SHR
//DSNAOINI DD PATH='/opt/IBM/ondemand/V9.5/config/cli.ini'
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//INPUT    DD DSN=PSF.SAPKSAM3(APKBANK),DISP=SHR
//CEEDUMP  DD SYSOUT=*.
//PARM     DD *
-h
ARCHIVE
-n
-g
appGrp
-s
INPUT
afp
/*

455

z/OS Server / Re: z/OS V2.3 Release Notes

« on: July 12, 2018, 07:56:22 AM »

Interesting.

1) I think 25 is the universal default port for for plain old non-encrypted SMTP.

2) So what's the line you have in your ars.cfg that points to arsodf.xml?  I'm curious.

Ed

456

z/OS Server / Re: z/OS V2.3 Release Notes

« on: July 10, 2018, 02:32:42 PM »

Hi Ed, ...You mentioned the parameter SRVR_ODF_CFG . We don't have that parameter and the knowledge center indicates that this is a parameter for IBMi , not z/OS.
Could you please clarify?
Thanks.

Well, I thought I was going to google and point you right to the doc.  Wrong!

Okay, that's something for me to follow up on.

Anyway, on my 9.5 system I've always had in ars.ini (not in the config) a line:

SRVR_ODF_CFG=/etc/ars/V950/arsodf.xml 

That file is in ASCII.   (Ugh)

To work with it I do a 3.17

17 Udlist      Print or display (to process) z/OS UNIX directory list

which takes me to a panel

z/OS UNIX Directory List Utility

Type in /etc/ars/V950 and I get a list of all of the members.

In front of arsodf.xml I type in EU for Edit a UTF-8 file

I can now work with that file.

Inside there is this:

<!--                                                     
   - These settings are used for all email notifications.
  -->                                                   
<SMTPServer>linuxbox.example.com</SMTPServer>     
<SMTPServerPort>25</SMTPServerPort>                     
<SSL>false</SSL>                                        

That tells ODF where to send emails for distribution.

Ed

457

Tips and Tricks / Re: JCL That I Find Handy

« on: July 06, 2018, 01:39:04 PM »

Supposed your userid's dot-profile is all set up for CMOD V9.5.

Now suppose you want to run some batch against your new V10.1 instance.

This JCL works fine for running against V9.5:

//JOBLIB   DD DISP=SHR,DSN=ARS.ARSV950.SARSLOAD       
//         DD DISP=SHR,DSN=DB2.V11R1M0.SDSNEXIT       
//         DD DISP=SHR,DSN=DB2.V11R1M0.SDSNLOAD       
//         DD DISP=SHR,DSN=DB2.V11R1M0.SDSNLOD2       
//STEP3    EXEC PGM=BPXBATCH,REGION=0M                 
//*                                                   
//*                                                   
//SYSPRINT DD SYSOUT=*                                 
//DSNAOINI DD PATH='/usr/lpp/ars/V9R5M0/config/cli.ini'
//ARSBIN   DD PATH='/usr/lpp/ars/V9R5M0/bin'           
//SYSOUT   DD SYSOUT=*                                 
//STDERR   DD SYSOUT=*                                 
//STDOUT   DD SYSOUT=*                                 
//STDPARM DD *                                         
SH  /usr/lpp/ars/V9R5M0/bin/arsdb    -I ARCH950 -mv   
/*                                                     

However, even though you change everything in the JCL to point to the V10.1 instance you get RC=256 and the error message:

ARS0013E DB Error: Warning:  Unexpected SQL_NO_DATA -- SQLSTATE=N/A, SQLCODE=100, File=arsmvsie.c, Line=1048
arsdb: ARS4012E Unable to initialize environment. The return code is 6         

//JOBLIB   DD DISP=SHR,DSN=ARS.ARSV1010.SARSLOAD       
//         DD DISP=SHR,DSN=DB2.V12R1M0.SDSNEXIT         
//         DD DISP=SHR,DSN=DB2.V12R1M0.SDSNLOAD         
//         DD DISP=SHR,DSN=DB2.V12R1M0.SDSNLOD2         
//STEP3    EXEC PGM=BPXBATCH,REGION=0M                 
//*                                                     
//*                                                     
//SYSPRINT DD SYSOUT=*                                 
//DSNAOINI DD PATH='/etc/ars/V1010/cli.ini'             
//ARSBIN   DD PATH='/usr/lpp/ars/V10R1M0/bin'           
//SYSOUT   DD SYSOUT=*                                 
//STDERR   DD SYSOUT=*                                 
//STDOUT   DD SYSOUT=*                                 
//STDPARM DD *                                         
SH  /usr/lpp/ars/V10R1M0/bin/arsdb    -I ARCH1010 -mv   
/*                                                     

The trick is to add the exports:

//STEP3    EXEC PGM=BPXBATCH,REGION=0M                     
//*                                                         
//*                                                         
//SYSPRINT DD SYSOUT=*                                     
//SYSOUT   DD SYSOUT=*                                     
//STDERR   DD SYSOUT=*                                     
//STDOUT   DD SYSOUT=*                                     
//STDPARM DD *                                             
SH                                                         
export DSNAOINI=/etc/ars/V1010/cli.ini;                     
export STEPLIB=DB2.V12R1M0.SDSNLOD2:DB2.V12R1M0.SDSNLOAD;   
/usr/lpp/ars/V10R1M0/bin/arsdb    -I ARCH1010 -mv;         
/*                                                         

Ed

458

z/OS Server / Performance Enhancement Available

« on: July 05, 2018, 02:30:47 PM »

APAR PI98845 adds the following to V10.1:

**************************************************************** 
* USERS AFFECTED: All Content Manager OnDemand for z/OS        * 
*                 10.1 using arsusec                           * 
**************************************************************** 
* PROBLEM DESCRIPTION: Provide an AMODE 64 sample arsusec      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
**************************************************************** 
With CMOD 10.1, the ARSSOCKD server runs as a 64-bit             
application.  In order to support existing AMODE 31 exits, glue   
code is provided at the cost of additional overhead.  In order   
to eliminate that cost for the arsusec exit, a sample AMODE 64   
arsusec assembler exit is provided.                               

459

z/OS Server / Re: CMOD Extraction of data

« on: July 03, 2018, 09:48:10 AM »

...we tend to bend the rules a bit to get things done quicker and easier.

Shriek!!!   



Ed

460

z/OS Server / Re: CMOD Extraction of data

« on: June 27, 2018, 11:01:37 AM »

Or maybe instead of worrying about file transfers and such you could load directly from z/OS -> any other platform.

You would have to install the same level of arsload as you're running on Linux, i.e. V10 -> V10, but no configuration would be needed.  Just lay down the code, point arsload to the other box and let 'er rip.

Yes, I know there may be a cost for the software involved on z if you needed a newer level, but I'd think it would make things much simpler.

Ed

461

z/OS Server / Indexer parm tightened up

« on: June 26, 2018, 08:59:43 AM »

If you see this:


 2018-06-21 08:48:47.176639: ARS5481I TRIGGER1=*,1,X'F1',TYPE=(GROUP)
 2018-06-21 08:48:47.176654: ARS5481I FIELD1=0,2,8,(TRIGGER=1,BASE=0)
 2018-06-21 08:48:47.176663: ARS5481I INDEX1='SEGMENT_NUMBER',FIELD1,(TYPE=GROUP,BREAK=NO)
 2018-06-21 08:48:47.176677: ARS5481I INDEX2='REPORT_DATE',FIELD1,(TYPE=GROUP,BREAK=NO)
 2018-06-21 08:48:47.176685: ARS5481I INDEX3='PAGE_NO',FIELD1,(TYPE=GROUPRANGE)
 2018-06-21 08:48:47.176746: ARS1146I Loaded 0 rows into the database

2018-06-21 08:48:47.176646: ARS5488E INVALID INDEXING PARM. ERROR OCCURS NEAR TYPE


Note the message, error occurs near TYPE.  (This really should be a mixed case message, it's in the works.)

Then the solution is to change

TRIGGER1=*,1,X'F1',TYPE=(GROUP)

to

TRIGGER1=*,1,X'F1',(TYPE=GROUP)

Ed

462

MP Server / Re: ODWEK - OnDemand slow retrievals when arsmaint is running

« on: June 19, 2018, 10:46:20 AM »

The only time I've seen ARSMAINT expiration suddenly running a long time is when a migration from another platform to CMOD was performed some years ago (say 7 for example).

At that time a lot of docs were all set to expire on the same date.

In 7 years' time everyone forgot (or was no longer there) that there was a big expiration coming up.

Suddenly, tons of expiration processing.

Oh no!  Is expiration processing running wild?

Are things getting expired that aren't supposed to be expired?

No, it was an unexpected increase in volume.

This is what we call the "pig in a python" problem.

Ed

463

z/OS Server / CMOD has exposed the following error in h/w compression/decompression

« on: June 15, 2018, 07:20:37 AM »

OA55725

ERROR DESCRIPTION:                                           
zLib deflate() call returns Z_STREAM_ERROR (RC=-2) with a     
z_stream *msg = System Error 003. This is a translated message
that is generated from a RC = x'C' RSN = x'XXXX0206' from     
FPZ4ABC, compression driver. This return code / reason code   
combination indicates that the generated compression output is
larger than the internal zEDC buffer.                         

464

z/OS Server / CMOD has exposed the following error in h/w compression/decompression

« on: June 15, 2018, 07:20:05 AM »

OA55725

ERROR DESCRIPTION:                                           
zLib deflate() call returns Z_STREAM_ERROR (RC=-2) with a     
z_stream *msg = System Error 003. This is a translated message
that is generated from a RC = x'C' RSN = x'XXXX0206' from     
FPZ4ABC, compression driver. This return code / reason code   
combination indicates that the generated compression output is
larger than the internal zEDC buffer.                         

465

Windows Client / Re: documents rotated when viewed in client v. 10.1

« on: June 07, 2018, 11:05:41 AM »

Try the 10.1.0.3 client.

I don't have the readme in front of me, but this sounds somewhat familiar.

Ed