Messages

1

z/OS Server / Re: ARSLOAD JCL Input from OMVS/USS

« on: July 13, 2023, 05:17:27 AM »

Thank you Ed  ,
By Any chance Field value length can be extended or supported Until 50 to 75K  length ?

2

z/OS Server / Re: ARSLOAD JCL Input from OMVS/USS

« on: July 11, 2023, 01:10:04 AM »

thank you ,  Identified issue . UTF-8 is Not accepted properly , We need to give IBM 1047 code page only when  Index file is build using xml indexer .

One last question , What is max length of filed that can be defined  in Application group  ?>

3

z/OS Server / Re: ARSLOAD JCL Input from OMVS/USS

« on: July 05, 2023, 10:56:13 AM »

Changed parms and got below error ,
removed -S option as it is not taking USS path ,instead  used -V .gave different error. hope fully will get fixed  .

//STEP1    EXEC PGM=ARSLOAD,REGION=0M,                     
//          PARM=('/-h ARSDBASE -g BMH-PMT -a BMH-PMT -nfE
//                -v /tmp/temp1/OnDemand-Outgoing.xml.in')
//DSNAOINI DD PATH='/ondemand/CPUG/parms/cli.ini'         
//ARSBIN   DD PATH='/usr/lpp1/ars/d2/bin'                                       
//SYSPRINT DD SYSOUT=*                                     
//SYSOUT   DD SYSOUT=*                                     
//INPSTATS   DD SYSOUT=*
//INDSTATS   DD SYSOUT=* 
//STDERR     DD SYSOUT=* 
//STDOUT     DD SYSOUT=* 
//SYSUDUMP   DD SYSOUT=* 
//CEEDUMP  DD SYSOUT=*             

2023-07-05 17:47:17.204960: ARS7732E A parsing error occurred in file /tmp/temp 1/OnDemand-Outgoing.xml.in, Line 2, Column 1:
invalid document structure                                                     
2023-07-05 17:47:17.205192: ARS4311E Loading failed                           
2023-07-05 17:47:17.205200: ARS4318E Processing failed for file >/tmp/temp1/OnD emand-Outgoing.xml.in<
2023-07-05 17:47:17.210905: ARS4327E Processing has stopped.  The remaining fil es will NOT be processed.
                       

4

z/OS Server / Re: ARSLOAD JCL Input from OMVS/USS

« on: July 04, 2023, 11:08:39 AM »

I also tried to Add Different XML declarations  ,All of them are failed with Same error .
Any One have suggestions 

5

z/OS Server / Re: ARSLOAD JCL Input from OMVS/USS

« on: June 30, 2023, 12:27:47 PM »

thank you Maw  ,  Here is OBJINPT  DD statement is refers to Xml file  .But it get failed with RC 06.  Not sure why it is tryign tot ake temp file different every time different even after providing path  and file name .

//          PARM=('/-h ARSDBASE -g FP -a FP -nfvE         
//                -s INPUT /tmp/arsload.temp')                       
//DSNAOINI DD PATH='/ondemand/x1/parms/cli.ini'                   
//ARSBIN   DD PATH='/usr/lpp1/ars/d2/bin'                           
//INPUT    DD PATH='/BOX/temp1/OnDemand-Outgoing.xml.in',           
//             PATHOPTS=(ORDONLY),                                   
//             PATHDISP=(KEEP,KEEP)                                 
//SYSPRINT DD SYSOUT=*                                               
//SYSOUT   DD SYSOUT=*                                               
//INPSTATS   DD SYSOUT=*                                             
//INDSTATS   DD SYSOUT=*                                             
//STDERR     DD SYSOUT=*                                             
//STDOUT     DD SYSOUT=*                                             
//SYSUDUMP   DD SYSOUT=*                                             
//CEEDUMP  DD SYSOUT=*         

SYSOUT :

2023-06-30 18:49:20.860013: ARS7732E A parsing error occurred in file /tmp//1717 1355.000001890DAFDEA5, Line 0, Column 0:
unable to open primary document entity '/tmp//17171355.000001890DAFDEA5'       
2023-06-30 18:49:20.860378: ARS4311E Loading failed                             
2023-06-30 18:49:20.860384: ARS4318E Processing failed for file >/tmp//17171355. .000001890DAFDEA5 (DD:INPUT-...PATH=.SPECIFIED...)< 
2023-06-30 18:49:20.866356: ARS4327E Processing has stopped.  The remaining files will NOT be processed.

                                     

6

z/OS Server / ARSLOAD JCL Input from OMVS/USS

« on: June 30, 2023, 09:05:00 AM »

HI team , 

WE have XML data which is Bigger than  250K in length and trying to store in CMOD for arching  , Since we cant get this in mainframe PS file  .we have delivered to OMVS and Expectation is to load directly from OMVS/USS Instead of copying to MVS  ,

Any one have suggestions Script /JCL needs to used to load data from OMVS 

7

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 29, 2023, 02:34:31 PM »

Sorry My bad , I was in hurry earlier ,

Our requirement Was to encrypt data before sending Out of our application , this is Audit requirement . But when we use basic cml data encrypt and send to CMOD load , it become difficult to decrypt and display record  And this function is Not supported On demand client . I am sure I didn't yet get full Knowledge On CMOD  ,I only started Working On this few week back  ,

based On comments in this thread  Amount of PCU that takes encrypt/decrypt create much more issues than solving  . So we have provide Audit teams document related to How data is stored in CMOD  so i think they might be happy with it for now ,  And we stopped encrypting data before loading to CMOD  . Not we are loading plain XML documents .

One of Infra team suggested this portal give best response and lot of education . 

coming to topic continuation  . Now we are Able to generate index file  . is it possible to load file through OMVS/USS  using ARSLOAD  ?

When i tried to run arsload  it cant recognize those commands  .
Any further suggestions or documents  ?   the document which i have Only provide single example  .
https://www.ibm.com/support/pages/system/files/inline-files/Using%20the%20Content%20Manager%20OnDemand%20XML%20Indexer%2020210212.pdf

After feed back I went back and verified some information , i think Its not worth and amount of work involved

Honestly, I don't think anyone in this thread really understands what you're trying to do.  I'll recommend some more education and training for your team about what CMOD is, what it does, and how it does it.

The amount of work you're doing is far, far in excess of what is necessary to store XML data in CMOD.

-JD.

8

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 29, 2023, 11:57:38 AM »

After feed back I went back and verified some information , i think Its not worth and amount of work involved

And base64 isn't encryption.  Unless they're doing something bizarre like encrypting the data, converting the binary data to base64, then storing it as text.  Quite literally a waste of CPU and storage at every step...

-JD.

9

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 29, 2023, 11:55:31 AM »

we did that  , and they came back with usage of another tool which is not available in our packages  today

Recommend you open up a Sev 4 (Usage) case with CMOD support.

I'm not 100% clear on what you're trying to do and I'll probably want you to send in some doc.

Ed

10

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 12, 2023, 01:26:12 PM »

thank you . For details , Also Quick question ,


When Input xml file have Multiple xml document it is failing to read second root element (using XSLT)  and identifying Only  first one . .this is When I try to run indexer Xslt  .

Every record Starts with BARootexport . for example  :


<BARootexport ></BARootexport>
<BARootexport ></BARootexport>
<BARootexport ></BARootexport>
<BARootexport ></BARootexport>

Does it required to be Under
<root>
<BARootexport ></BARootexport>
<BARootexport ></BARootexport>
<BARootexport ></BARootexport>
<BARootexport ></BARootexport>
</root>

...

That issue aside...  XML is already supported by CMOD...  Why not use the native support to store the XML?

-JD.

It's been a long time but I loaded up a sample file which you can take a look at here:

http://www.odusergroup.org/forums/index.php/topic,2336.msg8998.html#msg8998

Ed

11

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 12, 2023, 01:23:17 PM »

It is  messaging audit rule to store any data that to be encoded  . .  If there is No other option We should opt for loading original xml data  itself ,

That's the first time I've ever heard of base64 encoding data for storage in CMOD...

Base64 is normally used for sending binary data through systems that only support text encoding (like eMail)...  What's the rationale for converting to Base64?  The other problem with Base64 is that it INCREASES the size of files, costing you more in storage...

That issue aside...  XML is already supported by CMOD...  Why not use the native support to store the XML?

-JD.

12

z/OS Server / Re: Encoded and OptionalAttribute fields to define in odindex

« on: June 09, 2023, 06:43:30 AM »

Justin,

thank you for comments, we are using base 64 encode while generating data from DB. and then transferred over to OMVS .

13

z/OS Server / Encoded and OptionalAttribute fields to define in odindex

« on: June 01, 2023, 04:23:48 PM »

Iam Quite New to CMOD and we started using Z/os CMOd to store XML Documents  and from application we creates specific Out put file(XML) and generated before we create indexe file.   ,In the original Input file  we extract Few fields for Indexing  and Entire message copy of swift written as Encoded filed   Also we add this in fields information as One of Index field expecting to global Search with %% . But this field is alone encoded format and Cant be read unless it is decoded  .
 
 
        <encodedDocument name="Record" format="TEXT"><xsl:value-of select="$MXRecord"/></encodedDocument>
But when we defined  Like below it not reading value at all  .Second is we use On demand client to view searched records , When we view this encoded text How to set up Client view actual xml after decoding  .

 

 <odindex>
                <xsl:attribute name="field">MXRecord</xsl:attribute>
                <xsl:attribute name="value">
                    <xsl:value-of select="document/MXRecord" />
                </xsl:attribute>
            </odindex>
 
Another Issue from Input XML is mos tof our Index fields are optionalAttribute and they can be Null as it depends On input data recoprds ,

Inout :
        <optionalAttribute name="Name"></optionalAttribute>
        <optionalAttribute name="Address">blablabla </optionalAttribute>

In indexer we defined like below,But it is Not reading correctly  ,
<odindex>
                <xsl:attribute name="field">AcctSvcrRef</xsl:attribute>
                <xsl:attribute name="value">
                    <xsl:value-of select="document/AcctSvcrRef" />
                </xsl:attribute>
            </odindex>


Any Help would be very helpfull.