Messages

1

Report Indexing / Re: APK462S A TRIGGER PARAMETER WAS SPECIFIED, BUT THE INPUT FILE IS ALREADY INDEXED

« on: May 17, 2022, 11:36:49 PM »

Hi Justin,
The report contained few lines starting with.
And somehow OnDemand treats it as Index information inside the document file itself.

¤ LÓÓ   130600000

When I removed these lines, the ACIF indexing succeeds.


Regards,
Nikesh P Joshi

2

Report Indexing / APK462S A TRIGGER PARAMETER WAS SPECIFIED, BUT THE INPUT FILE IS ALREADY INDEXED

« on: April 04, 2022, 04:16:27 AM »

Hi,
I am not sure if this topic was discussed before in this forum(I couldn't find any).

I am facing this issue when I try to load a Line data and convert it to AFP.

2022-04-04 12:14:17.560806: ARS4335I Server Version <10.1.0.9>  Operating System <Linux> <#1 SMP Wed Feb 16 12:17:35 UTC 2022.3.10.0-1160.59.1.el7.x86_64> Database <DB2> <11.01.0406>
2022-04-04 12:14:17.568812: ARS4339I Application Group >SE-VD-QGBIFTC0<
2022-04-04 12:14:17.568850: ARS4340I Application >SE-VD-QGBIFTC0<
2022-04-04 12:14:17.568873: ARS4341I Storage Set >ASG_POC_StorageSet<
2022-04-04 12:14:17.568894: ARS4342I Storage Node >ASGPOC<
2022-04-04 12:14:17.568915: ARS4347I Encryption >None<
2022-04-04 12:14:17.568970: ARS4302I Indexing started, 152678 bytes to process
                          : APK415I CC=YES
                          : APK415I CCTYPE=Z
                          : APK415I CONVERT=YES
                          : APK415I CPGID=850
                          : APK415I MCF2REF=CPCS
                          : APK415I TRC=YES
                          : APK415I FILEFORMAT=STREAM
                          : APK415I TRIGGER1=*,13,X'40D2D6D5E3D6D5D9E740',(TYPE=GROUP)
                          : APK415I FIELD1=0,28,3,(TRIGGER=1,BASE=0)
                          : APK415I INDEX1=X'D2D6D5E3D6D5D9',FIELD1,(TYPE=GROUP,BREAK=YES)
                          : APK415I DCFPAGENAMES=NO
                          : APK415I UNIQUEBNGS=YES
                          : APK415I IMAGEOUT=ASIS
                          : APK415I INDEXOBJ=GROUP
                          : APK415I INDEXSTARTBY=1
                          : APK415I INSERTIMM=NO
                          : APK415I FORMDEF=F1IF93
                          : APK415I FDEFLIB=/archive/cmod/resources_se-viewdirect/fdef
                          : APK415I PAGEDEF=P1IF93
                          : APK415I PDEFLIB=/archive/cmod/resources_se-viewdirect/pdef
                          : APK415I PSEGLIB=/archive/cmod/resources_se-viewdirect/pseg
                          : APK415I OVLYLIB=/archive/cmod/resources_se-viewdirect/ovly
                          : APK415I FONTLIB=/archive/cmod/resources_se-viewdirect/font
                          : APK415I RESTYPE=ALL
                          : APK415I INPUTDD=/archive/preproc/VIEWDIRECT_SE/LOAD/QGBIFTC0.D220316_ebcdic
                          : APK415I OUTPUTDD=/archive/preproc/VIEWDIRECT_SE/LOAD/QGBIFTC0.D220316_ebcdic.out
                          : APK415I INDEXDD=/archive/preproc/VIEWDIRECT_SE/LOAD/QGBIFTC0.D220316_ebcdic.ind
                          : APK415I RESOBJDD=/archive/preproc/VIEWDIRECT_SE/LOAD/QGBIFTC0.D220316_ebcdic.res
                          : APK462S A TRIGGER PARAMETER WAS SPECIFIED, BUT THE INPUT FILE IS ALREADY INDEXED.
                          : APK448S INDEXING WAS REQUESTED, BUT NO GROUP 'TRIGGERn' NOR ANY 'FIELD' BASED ON IT WAS SATISFIED WITHIN THE PAGE RANGE SPECIFIED BY THE INDEXSTARTBY PARAMETER.
                          : APK441I ACIF AT PH34181 HAS COMPLETED ABNORMALLY WITH RETURN CODE 16.
2022-04-04 12:14:17.602599: ARS4309E Indexing failed
2022-04-04 12:14:17.602650: ARS4318E Processing failed for file >QGBIFTC0.D220316_ebcdic<
2022-04-04 12:14:17.614662: ARS4327E Processing has stopped.  The remaining files will NOT be processed.

Please ignore "APK448S", even after fixing the Triggers and fields I get the same error "APK462S ".
I have never seen this message "APK462S A TRIGGER PARAMETER WAS SPECIFIED, BUT THE INPUT FILE IS ALREADY INDEXED" till now in CMOD.
When I look at the input data, it does contain some index information.
Do any of you have successfully loaded such Line data with Index information embedded to CMOD-MP and converted to AFP?

Please suggest.


Regards,
Nikesh

3

Workshops/webinars, and the like / Re: Webinar: Migrating ASG/Mobius Solutions to IBM CMOD: A 4 Step Approach

« on: February 20, 2020, 05:36:38 AM »

Hi,
Is the recording of this session available somewhere?


/Nikesh

4

MP Server / Re: Version control - CMOD Objects

« on: August 19, 2019, 08:27:43 AM »

Thanks Justin and Russel for the response.

5

MP Server / Version control - CMOD Objects

« on: August 14, 2019, 02:46:59 AM »

Hi Guys,
Have anyone tried Version Control of CMOD Objects?
It it really possible and useful?

1. Extracting the CMOD Objects using arsxml and pushing to a GIT repo.
2. Use the xml for deploying objects to higher environments (instead of Export option in Administrator)?

The whole idea gets complicated when it comes to deleting an object.
Any suggestions and comments would be of great help.

/Nikesh

6

z/OS Server / Re: An example of a file too big to load

« on: June 17, 2019, 03:13:14 AM »

Hi Ed,
I have also done some testing with the maximum file size.

It also depends on number of documents in one report file and it's compression rate.
If one document creates more than 26 objects(whatever the object size be), then also CMOD issues this message.
Please give a try - Create a very big report file containing just 1 document - Set the Object size to 10,000K. The load would fail with the same error message from CMOD.
Considering 90% compression.
With a 10,000K object size we can store only upto 2.4GB report file.




/Nikesh PJ

7

MP Server / Re: Loading AFP document using Generic Indexer

« on: March 02, 2019, 02:18:41 AM »

Thank you.

8

MP Server / Loading AFP document using Generic Indexer

« on: March 01, 2019, 09:20:34 AM »

Hi,
I am trying to load a line data (EBCDIC) report file as AFP using Generic Indexer.

I have these files.
report.out        - Actual report file in EBCDIC format
report.out.ind  - Index file with all the indexes and values
report.out.res  - Resource file, extracted from already loaded document using arsdoc get -a

I am able to load the document using 

/opt/ibm/ondemand/V9.5/bin/arsload -h U3AE21 -u user -p pwd -g <AG> -a <APP> -n -X G report.out

But the AFP document doesn't look as it should.
It doesn't look like the document loaded using ACIF 

Please help me here. What am I missing here ?

-Nikesh PJ

9

MP Server / Re: How to delete single statements from a CMOD Load File

« on: January 08, 2019, 03:03:21 AM »

I have done an actual unload of one logical document from a load.
But it is a bit of manual process.
1. Extract the document and indexer file using "arsdoc get"
2. Find of which logical document (metadata and offset  details from the indexer file you want to unload)
3. Remove the content from the Reportfile(using the offset details)
4. Remove the metadata from the indexer file.
5. Change the offset for the other logical documents.
6. Load this report file and index file again to OD.
7. Unload the Previous load.

I know that this is not someone would suggest. But this helps