Encoded and OptionalAttribute fields to define in odindex

[New-Z/osCMODuser]

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.

[Justin Derrick]

So...  A few things...

You haven't described how the documents are 'encoded'.  Can you give us more information on that?  Remember that CMOD is simply a repository, and anything you load will be returned to you in the same format (with minor exceptions for document transforms at load time like line data to AFP and AFP to PDF).

Second, CMOD doesn't like 'null' fields, as it's ambiguous, and makes documents harder to find in the future.  If there's no way to avoid empty fields, then consider setting a default value in the CMOD Admin Client instead of trying to insert empty fields into CMOD.

-JD.

[New-Z/osCMODuser]

Justin,

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

[Justin Derrick]

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.

[Ed_Arnold]

...

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

[New-Z/osCMODuser]

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.

[New-Z/osCMODuser]

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

[Ed_Arnold]

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

[Darrell Bryant]

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 ,

Content Manager OnDemand supports encryption at rest.
See https://www.ibm.com/support/pages/ibm-content-manager-ondemand-native-encryption

[Justin Derrick]

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.

[New-Z/osCMODuser]

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

[New-Z/osCMODuser]

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.

[Justin Derrick]

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.

[New-Z/osCMODuser]

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.