×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I am doing duplicate definition of XML to match to my file fields. Then Iam going to use EVAL-CORR to populate file data structure.
My XML is below:
In below example branch and product are referenced to brand_Template.branchcode and brand_Template.productcode respectively.
Since brand_Template has got DIM(999) Is my definition correct for branch and product in File1_Template?
Only two elements branch and product belong to array data structure (brand_Template) and rest come from anotehr data structure which is not an array. How do I handle dim(999)definition from brand_Template to these two elements in File1_template data structure?
XML data structure
===
d comp_Template...
d ds qualified based(dummy_ptr)
d brands likeds(brands_Template)
d source likeds(source_Template)
d contact likeds(contact_Template)
d risk likeds(risk_Template)
d
d brands_Template...
d DS qualified based(dummy_ptr)
d brand likeds(brand_Template) DIM(999)
d brand_Template DS qualified based(dummy_ptr)
d name 10a
d branchcode 5a
d productcode 6a
d name_Template ds qualified based(dummy_ptr)
d title 20a
d firstname 50a
d lastname 50a
---------------------------------------------------------------------
d ptrbrand s * inz(%Addr(brand_Template))
---------------------------------------------------------------------
* Defining duplicate XML version for secondary version
d File1_Template...
d ds qualified based(ptrbrand)
d branch like(brand_Template.branchcode)
d const
d product like(brand_Template.productcode)
d const
d fnam1 like(name_Template.firstname)
D const
D lnam2 like(name_Template.lastname)
D const
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
