Messages

76

MP Server / Re: Folder Searches

« on: July 06, 2017, 07:46:05 AM »

Always happy to help. 

77

MP Server / Re: Folder Searches

« on: July 06, 2017, 06:35:26 AM »

Couldn't you create a folder that lets you search on client name across the multiple AGs?

78

Report Indexing / Re: ARSLOAD Syntax for Using File Name to Index

« on: June 22, 2017, 12:59:39 PM »

What do you have in the .ind file when you submit the file to load?

79

Report Indexing / Re: PDF Indexer with separate index data

« on: June 22, 2017, 12:57:07 PM »

Since you'll probably be using the RESTYPE parameter you would have to convert your indexing in the .IND file to the non-generic format:
TRIGGER1=
FIELD1=
FIELD2=
INDEX1=
INDEX2=

I've haven't set it up myself but you probably could use ARSPDOCI with a parm file in an almost similar manner as you use the generic loader with the .ind file.

80

Report Indexing / Re: ARSLOAD Syntax for Using File Name to Index

« on: June 22, 2017, 05:29:33 AM »

Any chance you tried the following?
-G FORMS –B “FOR.1FLD.2FLD.3FLD.4FLD”
or just
–B “FOR.1FLD.2FLD.3FLD.4FLD”    since CMOD defaults to the forms field.

I've had similar issues as you and for some reason this seemed to clear it up.

81

z/OS Server / Re: Access CMOD across domain

« on: June 14, 2017, 04:48:55 AM »

That would be a question for your network group.  They'll have to open a path from domain B to domain A for your source IP and port to your CMOD IP and port.  I'm sure there's plenty of firewalls in your way.

82

MP Server / Re: Calling PDF Indexing Guru's

« on: June 08, 2017, 05:28:28 AM »

Does the vendor have the ability to reformat that footer?  Possibly move MEMOSTMT to just after OnDemand?

83

MP Server / Re: Large .txt file with No indexing

« on: May 10, 2017, 05:11:50 AM »

Did you try indexing only using constants?  We've done that a number of times and it doesn't involve pulling indexes from the document.
Load date is a good one to start with as you only need to specify the t in the load information.
Usually we throw in a title or report name for good measure.  Looks like this:
CC=YES
CCTYPE=A
CONVERT=NO
CPGID=500
MCF2REF=CPCS
TRC=NO
FILEFORMAT=RECORD,261
FIELD1=X'C8C5F8F9F9F6'           /* HE8996  */
INDEX1=X'D985979699A36DD5819485',FIELD1,(TYPE=GROUP,BREAK=NO)   /* Report_Name */
DCFPAGENAMES=NO
UNIQUEBNGS=YES
IMAGEOUT=ASIS
INDEXOBJ=ALL
INDEXSTARTBY=1
INSERTIMM=NO
RESTYPE=NONE

84

z/OS Server / Re: Converting ARSBDIST to new ARSODF options

« on: April 18, 2017, 06:12:40 AM »

From my experience this is the only that format works for me (9.5.0.7) .
//ARSBDIST EXEC PGM=ARSODF,REGION=0M,
//    PARM=('/-I CMODT -d "RM198 ODF TEST" -r rm198')             
//STEPLIB  DD DSN=NSSP#.CMOD.SARSLOAD,DISP=SHR                       
//         INCLUDE MEMBER=DW11LOAD                                   
//DSNAOINI DD PATH='/usr/lpp/ars/V9R5M7/config/bdist.ini'           
//ARSBIN   DD PATH='/usr/lpp/ars/V9R5M7/bin'                         
//STATSOUT DD SYSOUT=*                                               
//SYSUDUMP DD SYSOUT=*                                               
//SYSOUT   DD SYSOUT=*                                               
//CEEDUMP  DD SYSOUT=*                                               
//ABNLIGNR DD DUMMY                                                 
//STATRPT  DD SYSOUT=*                                               
//ARSLOG   DD SYSOUT=*                 

85

z/OS Server / Re: ACIF indexer creates duplicate content inside the report

« on: April 07, 2017, 05:29:26 AM »

Can you tell us what version and level you are at?

86

z/OS Server / Re: ACIF indexer creates duplicate content inside the report

« on: April 04, 2017, 07:50:28 AM »

I can't imagine the ACIF indexer adding records to the content within the document.  Are you using input exits for the docs?

87

z/OS Server / Re: How to make fallback from upgrade?

« on: February 13, 2017, 09:42:45 AM »

Thanks, I was aware of the new format for the SLxx tables using the DB2 date format.  We just never saw the requirement to run arssyscr in the instructions to upgrade from 8.5 to 9.5 so we never ran it.

88

z/OS Server / Re: How to make fallback from upgrade?

« on: February 10, 2017, 01:07:00 PM »

Thanks.  That could be handy in a number of occasions.
One thing I find interesting is we never ran into the SLxx issue.  Our existing SLxx tables never got modified with new column, only new instance created under 9.5 have the extra SLxx column.

89

z/OS Server / Re: How to make fallback from upgrade?

« on: February 10, 2017, 11:48:49 AM »

Sorry I missed much of this discussion.  The process I listed was meant more for an immediate backout.  Anything loaded after the initial migration would be lost after falling back  In our one of our cases it was dummy data for test loads as part of the verification process which we deemed expendable.  If you started loading production data you're in a different situation and the process I listed less optimal.   We actually ran into this situation with another customer and the fallback was much more difficult, though not impossible.   In a very basic summary: We had to identify all loads processed after the migration which, fortunately, wasn't an overwhelming number.  Did a DB2 unload of the ARSRES table to help identify any new resources loaded during that period.  Ran our fallback procedure which reverts all system tables to pre migration status but doesn't touch the index data.  We then had to increment the LOAD_ID and RESGRP manually for each Application group that had been loaded in to cover the loads made after migration.  Then we added the new entries to ARSRES using the ARSRES unload we did earlier.  Since everything we do loads through OAM nothing is set to expire by Load and ARSLOAD isn't an issue.

90

z/OS Server / Re: Load ID Format - Help

« on: January 20, 2017, 01:21:14 PM »

The load ID format can be found in the V9.5 Administration guide under ARSADMIN -L parameter description.
Input file name looks consistent with what we get in our load messages.