JBI4CICS
|
|
fmartin
|
Hi,
I have to do an integration with a mainframe with OS/390 runing a CICS transactional system. I would like to try the JBI4CICS component, together with the CICS Transactional gateway. the problem is that in that mainframe they do not use Cobol, they user PL/1, and I'm not sure if this component will work. As far as I understand, it does not matter if the program is Cobol or PL/1, at the end is a CICS service after compilation, but the specs for the JBI4CICS need a Copy Cobol file to generate the WSDL according to that interface. The question at the end is: Is it possible to use this component (JBI4CICS) if the CICS service in the mainframe is developed with PL/1? If they provide a CPY file even if the program is developed with PL/1, will this work? (maybe the last sentence does not make any sense, but I do not know that much of all this CICS stuff) Thanks, Fernando --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
||||||||||||||||
stephen fabian
|
In order to create any type of generated code from say COBOL or PL/I
source, it has to be parsed. The syntax of COBOL and PL/I are vastly different so a COBOL parser can not read PL/I. You would have to write a "pre-process" to convert PL/I record layout into COBOL format and then use to generate the wsdl. Fernando Martin wrote: > Hi, > > I have to do an integration with a mainframe with OS/390 runing a CICS transactional system. I would like to try the JBI4CICS component, together with the CICS Transactional gateway. > > the problem is that in that mainframe they do not use Cobol, they user PL/1, and I'm not sure if this component will work. As far as I understand, it does not matter if the program is Cobol or PL/1, at the end is a CICS service after compilation, but the specs for the JBI4CICS need a Copy Cobol file to generate the WSDL according to that interface. > > The question at the end is: Is it possible to use this component (JBI4CICS) if the CICS service in the mainframe is developed with PL/1? If they provide a CPY file even if the program is developed with PL/1, will this work? (maybe the last sentence does not make any sense, but I do not know that much of all this CICS stuff) > > Thanks, > Fernando > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
||||||||||||||||
|
fmartin
|
In reply to this post
by fmartin
Thanks for the answer. I di not understand exactly what you mean, but I guess that if in the mainframe they develop a "process" in PL/I, I cannot have a CPY file that I can use to generate the wsld straightforward with JBI4CICS.
Any suggestion? Should I better create a java client using CTG to access the ECI Service? I'm a bit lost with the mainframe, but I need to find a solution for the integration. They can only tell me that there is no Cobol compiler in the mainframe, and they can only do PL/I Thanks in advance, Fernando -----Original message----- From: Stephen Fabian [hidden email] Date: Thu, 08 Oct 2009 15:39:52 +0200 To: [hidden email] Subject: Re: JBI4CICS > In order to create any type of generated code from say COBOL or PL/I > source, it has to be parsed. The syntax of COBOL and PL/I are vastly > different so a COBOL parser can not read PL/I. You would have to write > a "pre-process" to convert PL/I record layout into COBOL format and then > use to generate the wsdl. > > Fernando Martin wrote: > > Hi, > > > > I have to do an integration with a mainframe with OS/390 runing a CICS transactional system. I would like to try the JBI4CICS component, together with the CICS Transactional gateway. > > > > the problem is that in that mainframe they do not use Cobol, they user PL/1, and I'm not sure if this component will work. As far as I understand, it does not matter if the program is Cobol or PL/1, at the end is a CICS service after compilation, but the specs for the JBI4CICS need a Copy Cobol file to generate the WSDL according to that interface. > > > > The question at the end is: Is it possible to use this component (JBI4CICS) if the CICS service in the mainframe is developed with PL/1? If they provide a CPY file even if the program is developed with PL/1, will this work? (maybe the last sentence does not make any sense, but I do not know that much of all this CICS stuff) > > > > Thanks, > > Fernando > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [hidden email] > > For additional commands, e-mail: [hidden email] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
stephen fabian
|
It's not a trivial problem. I found this on the net re: pl/i parser:
http://www.cocolab.com/en/parse_pl1.html You can create the wsdl manually but if the ECI entry changes it will have to be redone manually. Do you have the PL/I copy book available to you? Fernando Martin wrote: > Thanks for the answer. I di not understand exactly what you mean, but I guess that if in the mainframe they develop a "process" in PL/I, I cannot have a CPY file that I can use to generate the wsld straightforward with JBI4CICS. > > Any suggestion? Should I better create a java client using CTG to access the ECI Service? I'm a bit lost with the mainframe, but I need to find a solution for the integration. > They can only tell me that there is no Cobol compiler in the mainframe, and they can only do PL/I > > Thanks in advance, > Fernando > -----Original message----- > From: Stephen Fabian [hidden email] > Date: Thu, 08 Oct 2009 15:39:52 +0200 > To: [hidden email] > Subject: Re: JBI4CICS > > >> In order to create any type of generated code from say COBOL or PL/I >> source, it has to be parsed. The syntax of COBOL and PL/I are vastly >> different so a COBOL parser can not read PL/I. You would have to write >> a "pre-process" to convert PL/I record layout into COBOL format and then >> use to generate the wsdl. >> >> Fernando Martin wrote: >> >>> Hi, >>> >>> I have to do an integration with a mainframe with OS/390 runing a CICS transactional system. I would like to try the JBI4CICS component, together with the CICS Transactional gateway. >>> >>> the problem is that in that mainframe they do not use Cobol, they user PL/1, and I'm not sure if this component will work. As far as I understand, it does not matter if the program is Cobol or PL/1, at the end is a CICS service after compilation, but the specs for the JBI4CICS need a Copy Cobol file to generate the WSDL according to that interface. >>> >>> The question at the end is: Is it possible to use this component (JBI4CICS) if the CICS service in the mainframe is developed with PL/1? If they provide a CPY file even if the program is developed with PL/1, will this work? (maybe the last sentence does not make any sense, but I do not know that much of all this CICS stuff) >>> >>> Thanks, >>> Fernando >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [hidden email] >>> For additional commands, e-mail: [hidden email] >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [hidden email] >> For additional commands, e-mail: [hidden email] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
||||||||||||||||
|
fmartin
|
In reply to this post
by fmartin
No, I do not have it, since we are still preparing a solution for this interface. We want to do a proof of concept, but for that I need to know what to request them. At the end, the ECI should not change.
So, If I understood you, the can create the PL/I, and somehow we can manually create the wsdl by understanding the "input" and "output" fields of the ECI interface. Am I correct saying this? If so, where does the PL/I parser plays its role? Thanks a lot for the answers, I really appreciate it. Fernando -----Original message----- From: Stephen Fabian [hidden email] Date: Thu, 08 Oct 2009 19:19:25 +0200 To: [hidden email] Subject: Re: JBI4CICS > It's not a trivial problem. I found this on the net re: pl/i parser: > http://www.cocolab.com/en/parse_pl1.html > > You can create the wsdl manually but if the ECI entry changes it will > have to be redone manually. Do you have the PL/I copy book available to > you? > > Fernando Martin wrote: > > Thanks for the answer. I di not understand exactly what you mean, but I guess that if in the mainframe they develop a "process" in PL/I, I cannot have a CPY file that I can use to generate the wsld straightforward with JBI4CICS. > > > > Any suggestion? Should I better create a java client using CTG to access the ECI Service? I'm a bit lost with the mainframe, but I need to find a solution for the integration. > > They can only tell me that there is no Cobol compiler in the mainframe, and they can only do PL/I > > > > Thanks in advance, > > Fernando > > -----Original message----- > > From: Stephen Fabian [hidden email] > > Date: Thu, 08 Oct 2009 15:39:52 +0200 > > To: [hidden email] > > Subject: Re: JBI4CICS > > > > > >> In order to create any type of generated code from say COBOL or PL/I > >> source, it has to be parsed. The syntax of COBOL and PL/I are vastly > >> different so a COBOL parser can not read PL/I. You would have to write > >> a "pre-process" to convert PL/I record layout into COBOL format and then > >> use to generate the wsdl. > >> > >> Fernando Martin wrote: > >> > >>> Hi, > >>> > >>> I have to do an integration with a mainframe with OS/390 runing a CICS transactional system. I would like to try the JBI4CICS component, together with the CICS Transactional gateway. > >>> > >>> the problem is that in that mainframe they do not use Cobol, they user PL/1, and I'm not sure if this component will work. As far as I understand, it does not matter if the program is Cobol or PL/1, at the end is a CICS service after compilation, but the specs for the JBI4CICS need a Copy Cobol file to generate the WSDL according to that interface. > >>> > >>> The question at the end is: Is it possible to use this component (JBI4CICS) if the CICS service in the mainframe is developed with PL/1? If they provide a CPY file even if the program is developed with PL/1, will this work? (maybe the last sentence does not make any sense, but I do not know that much of all this CICS stuff) > >>> > >>> Thanks, > >>> Fernando > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [hidden email] > >>> For additional commands, e-mail: [hidden email] > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [hidden email] > >> For additional commands, e-mail: [hidden email] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [hidden email] > > For additional commands, e-mail: [hidden email] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
||||||||||||||||
|
stephen fabian
|
Some javascript/style in this post has been disabled (why?)
If you do things manually you don't need the parser, but for a
production setup it is highly recommended.You can setup the wsdl manually. The transaction gateway maybe of assistance to you as well, but I don't have any docs to look through. Your solution will be much more professional with an automated parser even if the interlace will not change often. What if you customer needs to repeat this process for multiple apps, it soon becomes time consuming and error prone. Fernando Martin wrote: No, I do not have it, since we are still preparing a solution for this interface. We want to do a proof of concept, but for that I need to know what to request them. At the end, the ECI should not change. So, If I understood you, the can create the PL/I, and somehow we can manually create the wsdl by understanding the "input" and "output" fields of the ECI interface. Am I correct saying this? If so, where does the PL/I parser plays its role? Thanks a lot for the answers, I really appreciate it. Fernando -----Original message----- From: Stephen Fabian [hidden email] Date: Thu, 08 Oct 2009 19:19:25 +0200 To: [hidden email] Subject: Re: JBI4CICSIt's not a trivial problem. I found this on the net re: pl/i parser: http://www.cocolab.com/en/parse_pl1.html You can create the wsdl manually but if the ECI entry changes it will have to be redone manually. Do you have the PL/I copy book available to you? Fernando Martin wrote:Thanks for the answer. I di not understand exactly what you mean, but I guess that if in the mainframe they develop a "process" in PL/I, I cannot have a CPY file that I can use to generate the wsld straightforward with JBI4CICS. Any suggestion? Should I better create a java client using CTG to access the ECI Service? I'm a bit lost with the mainframe, but I need to find a solution for the integration. They can only tell me that there is no Cobol compiler in the mainframe, and they can only do PL/I Thanks in advance, Fernando -----Original message----- From: Stephen Fabian [hidden email] Date: Thu, 08 Oct 2009 15:39:52 +0200 To: [hidden email] Subject: Re: JBI4CICS |
||||||||||||||||
Mark S White
|
Some javascript/style in this post has been disabled (why?)
With this search string in Google: "pl1 to cobol conversion" you can
find numeroustools that could convert the PL1 definitions of the input and output into Cobol definitions. You could then feed the Cobol definitions into the design time of the JBI4CICS component to generate the WSDL. Stephen Fabian wrote: If you do things manually you don't need the parser, but for a production setup it is highly recommended.--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
