| Author |
Message
|
| alerajeshh |
 Posted: Mon Apr 27, 2015 12:12 pm Post subject: Creating Multiple CICS Containers ?? |
 |
|
Acolyte
Joined: 19 Aug 2013
Posts: 55
|
When i send a request to CICS Request Node.. am going to get 200 different container collections... How to handle so many..and the container names are in format XXXXX0 XXXXX1 XXXXXX2 till 99 ..
There are around 3 containers like that ,with 99 ..I dont want to mention them on CICS Request node..if i do so, i need to create 200 message sets, which is really bad.
Is there any way when i get the response i can handle them..using esql.. am okay to write 200 lines of code for containers..
How to create multiple channel containers other than on CICS Request Node.. can it be possible to do in the esql after the CICS Node ??
and i dont want to create 200 message sets ..
help me |
|
| Back to top |
|
 |
| alerajeshh |
| Posted: Tue Apr 28, 2015 6:08 am Post subject: |
|
|
Acolyte
Joined: 19 Aug 2013
Posts: 55
|
any answers ?..
I just created DFDL using one cobol copybook response.. bt from CICS ,they are coming in CONTAINERS and there are 99 container for 3 types..
Is there any way we can do in DFDL to dynamically take the container name ? |
|
| Back to top |
|
|
| pmasters |
| Posted: Wed Apr 29, 2015 6:53 am Post subject: |
|
|
Novice
Joined: 19 Jul 2011
Posts: 14
|
Hiya - I must admit I'm not entirely clear what you're doing here. This is processing containers returned in the channel response that you are trying to assign DFDL models too?
You don't need to do this in the CICS node. Any containers not recognised in the response message parsing table will be treated as blob data which you can assign a type to later via esql or similar.
How many distinct message models do you have, and do you have a naming scheme you can use to correlate the container names with the correct model? If so, then you should be ok - it doesn't need to be mapped statically in the node though.
_________________
===========
Peter Masters |
|
| Back to top |
|
|
| alerajeshh |
| Posted: Wed Apr 29, 2015 6:58 am Post subject: |
|
|
Acolyte
Joined: 19 Aug 2013
Posts: 55
|
Am sorry, I havent given information.. So from CICS Request node am getting around 207 containers.. which are related like one kind of msg having 9 containers, and other one with 99 containers, and other one with 99..
so i created 3 message sets for each type.. and on the cics request node properties,, Response parsing tab.. do i need to add 207 container names (in the channel options) ,,
is there any way before the cics request node in esql can we mention these 207 container names ?? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 29, 2015 7:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| pmasters |
| Posted: Wed Apr 29, 2015 7:28 am Post subject: |
|
|
Novice
Joined: 19 Jul 2011
Posts: 14
|
So if this is about processing responses, this would be after the CICS node, rather than before it. The message assembly returned by the CICS node would have a series of containers represented as child messages within a Message Collection, each of which would be an unparsed BLOB bytestream.
You can parse these Blobs as DFDL messages using CREATE FIELD with a PARSE option to construct a new outgoing collection, naming the InputRoot.Collection.<container name>.BLOB.BLOB to get the input byte stream, and referring to the correct model.
_________________
===========
Peter Masters |
|
| Back to top |
|
|
|
|
