Messages

226

z/OS Server / Re: CMOD 8.5 IS OUT!!!!

« on: May 25, 2011, 07:24:42 AM »

We just hit a small snafu with the upgrade.  Nothing major but worth mentioning in the case someone else hits this problem.  When running the V8.5 arsdb command our lead technical was getting an exception error:

CEE3204S The system detected a protection exception (System Completion Code=0C4)
.
From entry point u_file_write_44_arsxh at compile unit offset +00000054
at entry offset +00000054 at address
10AFC424.

He could run the V8.4 arsdb command with no issues.
I found I was able to run the v8.5 arsdb command with no issues. 
When checking ulimits we discovered he had:
address space     36928k

and I had:
address space     172264k

After upping his address space the arsdb command works fine.  Safe to guess that the new arsdb is taking up a bit more space out there.

227

z/OS Server / Re: How to Archive Text File using parameter file in Z/OS

« on: May 19, 2011, 05:42:03 AM »

The generic indexer does let you reference a DD name on z/OS for the input file.  I only gave it a quick try with no luck but then again I didn't put much effort into getting it to work.

228

z/OS Server / Re: How to Archive Text File using parameter file in Z/OS

« on: May 18, 2011, 09:21:24 AM »

Hope I understood your question correctly.
The way I've archived text files with the generic indexer is to place the files, both the text file and the index paramater file in USS.  I seem to recall the generic indexer will only work against files in USS.
The index parm file contains the path and filename for the text file as GROUP_FILENAME.
Example for a single text file.  The file name is bldparms.ind :
CODEPAGE:500
GROUP_FIELD_NAME:Report_Title
GROUP_FIELD_VALUE:Install OnDemand client
GROUP_FIELD_NAME:Report_Date
GROUP_FIELD_VALUE:5/18/2011
GROUP_FIELD_NAME:Author
GROUP_FIELD_VALUE:Smith
GROUP_FIELD_NAME:Subject
GROUP_FIELD_VALUE:CMOD
GROUP_OFFSET:0
GROUP_LENGTH:0
GROUP_FILENAME:/etc/ond/32P/pcfile.input
The directory /etc/ond/32P would contain
.
..
pcfile.input
bldparms.ind

When I execute the command:
arsload -u smith -p xxxxx -h archive -a TEXTDOC -g PCDOCS -c /etc/ond/32P/temp /etc/ond/32P/bldparms

the text file will get loaded.

I do have a setup that would allow me to modify the parm file in z/OS and upload it to USS.
One member contains the parm file, lets say it's called PCDOCS:

CODEPAGE:500
GROUP_FIELD_NAME:Report_Title
GROUP_FIELD_VALUE:Install OnDemand client
GROUP_FIELD_NAME:Report_Date
GROUP_FIELD_VALUE:5/18/2011
GROUP_FIELD_NAME:Author
GROUP_FIELD_VALUE:Smith
GROUP_FIELD_NAME:Subject
GROUP_FIELD_VALUE:CMOD
GROUP_OFFSET:0
GROUP_LENGTH:0
GROUP_FILENAME:/etc/ond/32P/pcfile.input

My JCL will then copy it to the ZFS:

//COPYSTEP EXEC PGM=IKJEFT01
//OUTHFS   DD PATH='/etc/ond/32P/bldprms.ind',
//            PATHDISP=(KEEP,DELETE)
//*           PATHOPTS=(OWRONLY,OCREAT,OEXCL),
//*           PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
//* if bldnprms.tmp does not exist uncomment the previous 2 lines
//*           PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP)
//INMVS    DD DISP=SHR,DSN=HLQ.ONDEMAND.PCLOAD.JCL(PCDOCS)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
OCOPY INDD(INMVS) OUTDD(OUTHFS) TEXT CONVERT(NO) PATHOPTS(USE)
/*

One major "gotcha" I've discovered with this method is that the process pads the parmfile with blanks which causes the load process fail.  I had to create a rexx exec on the USS that would strip the blanks.
Hope this helps some

229

Report Indexing / Re: Converting from OS/390 to ACIF Indexer

« on: May 05, 2011, 11:14:20 AM »

In my experience you usually get those errors when your fileformat is off.  I would double check the input file that you are dropping in.  Maybe an EBCDIC- ASCII conversion issue?

230

z/OS Server / Re: CMOD 8.5 IS OUT!!!!

« on: April 15, 2011, 10:59:10 AM »

Great.  Thanks!   Good to know we won't be the alpha for this.  If you could, it would be appreciated if you could post any gotcha's that may pop up.  We're looking forward to this migration, some nice changes in this release.

231

z/OS Server / Re: CMOD 8.5 IS OUT!!!!

« on: April 13, 2011, 10:08:36 AM »

Is anyone running v 8.5 on z/OS 1.12?  We're looking at migrating to 8.5 and we have a z/OS 1.12 migration schedule right in the middle of it.

232

Report Indexing / Re: RECORDRANGE and GROUPRANGE

« on: December 03, 2010, 07:04:29 AM »

Correct

233

Report Indexing / Re: RECORDRANGE and GROUPRANGE

« on: December 01, 2010, 01:16:51 PM »

And to add to my previous post.  To use the index I have two fields defined:  Log_Time and Log_Time_end.  In the application under the Load Information tab in Preprocessor Parameters both those fields have Log_Time set as the Load ID name. 

234

Report Indexing / Re: RECORDRANGE and GROUPRANGE

« on: December 01, 2010, 12:59:09 PM »

Here is an example of GROUPRANGE.  This is indexing a large log file and the grouprange index will give me the start and end times for the log which are in the format hh:mm:ss 

FIELD1=0,12,6,(TRIGGER=1,BASE=0)
FIELD2=0,21,5,(TRIGGER=1,BASE=0)
FIELD3=*,*,8,(OFFSET=(27:34),MASK='##:##:##',ORDER=BYROW)
INDEX1=X'D985979699A36DD5819485',FIELD1,(TYPE=GROUP,BREAK=NO)     /* Report_Name */
INDEX2=X'D396876DC481A385',FIELD2,(TYPE=GROUP,BREAK=NO)           /* Log_Date    */
INDEX3=X'D396876DE3899485',FIELD3,(TYPE=GROUPRANGE,BREAK=NO)      /* Log_Time    */

235

z/OS Server / Re: ARSLOAD on a different system

« on: November 04, 2010, 11:47:52 AM »

Terrific!  Thanks for replying  That's exactly what I wanted to hear. 

236

Report Indexing / Re: CMOD Indexing - Newbie

« on: October 22, 2010, 10:54:38 AM »

Could be a typo in your post but I believe Trigger1 needs to be TRIGGER1=*,2,'APPLICATION: ',(TYPE=GROUP) if that was what you're aiming for(Trigger1 needs * for record number).  If you were shooting for TRIGGER2 I would go with TRIGGER2=*,2,'APPLICATION: ',(TYPE=FLOAT)

237

z/OS Server / ARSLOAD on a different system

« on: October 22, 2010, 10:40:06 AM »

We're running an 8.4 instance on z/OS.  We've noticed in various documentation that it's shown that ARSLOAD can be run in a different system and use TCP/IP to connect with the library and object server.  Does anybody here run their systems this way?  We're trying to design something along this line and, while seeing reference to it, we're not seeing any actuall "how to's".  Problem is we're not trying to go from z/OS to z/OS but from a distributed environment to z/OS.
Any help would be appreciated.