| Author |
Message |
Kausar
Guest
|
Posted:
Mon Oct 25, 2004 11:31 pm Post subject:
Calling .Net component from COBOL batch job [Non-CICS] OS/39 |
|
|
Hi,
In Host Initiated Processing scenario, we want to communicate from a
COBOL batch job [which is not CICS based ] to a .Net component. SNA
seems not to be an option for us here. The basic idea is: We want
business rules residing in a .Net component [using Biztalk Rules]
called from this COBOL batch job. Is there anyway i can achieve this?
Thanks in advance!
Kausar |
|
| Back to top |
|
 |
Anthony LaMark
Guest
|
Posted:
Tue Oct 26, 2004 4:40 am Post subject:
Re: Calling .Net component from COBOL batch job [Non-CICS] O |
|
|
Hi Kausar,
Check out eXc Software's (www.eXcSoftware.com) z/OS (MVS) WMI Event
Provider. It has an automation component. You could accomplish what you
want with a simple WTO in your Cobol programs.
"Kausar" <kausar.mohammad@gmail.com> wrote in message
news:d567f5b8.0410251031.7ddb663b@posting.google.com...
| Quote: | Hi,
In Host Initiated Processing scenario, we want to communicate from a
COBOL batch job [which is not CICS based ] to a .Net component. SNA
seems not to be an option for us here. The basic idea is: We want
business rules residing in a .Net component [using Biztalk Rules]
called from this COBOL batch job. Is there anyway i can achieve this?
Thanks in advance!
Kausar |
|
|
| Back to top |
|
 |
Neil Pike
Guest
|
Posted:
Tue Oct 26, 2004 4:42 pm Post subject:
Re: Calling .Net component from COBOL batch job [Non-CICS] O |
|
|
Kausar,
Several choices :-
1. APPC (SNA) which you say isn't an option, but not why. The Cobol program
would make an APPC connection to a program running on a server that listened on
APPC via a HIS server. With HIS2004 and Enterprise Extender this could all run
over IP.
2. TCP-IP sockets. Not sure if Cobol has built-in IP sockets stuff these
days - but if not an assembler module could act as an interface. Talking to a
program on the server that's listening on IP sockets.
Both the above involve some fairly low-level coding.
3. Use middle-ware. E.g. IBM MQ Series. Cobol (Mainframe) and Server
(C/VB/whatever) programs could communicate using MQ Series. Using this option
has a lot less low-level coding as all the comms/retry type stuff is handled by
MQ Series.
| Quote: | In Host Initiated Processing scenario, we want to communicate from a
COBOL batch job [which is not CICS based ] to a .Net component. SNA
seems not to be an option for us here. The basic idea is: We want
business rules residing in a .Net component [using Biztalk Rules]
called from this COBOL batch job. Is there anyway i can achieve this?
Thanks in advance!
Kausar
|
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise) |
|
| Back to top |
|
 |
Kausar
Guest
|
Posted:
Tue Oct 26, 2004 11:29 pm Post subject:
Re: Calling .Net component from COBOL batch job [Non-CICS] O |
|
|
Thanks Anthony for the response, I will take look at it.
"Anthony LaMark" wrote:
| Quote: | Hi Kausar,
Check out eXc Software's (www.eXcSoftware.com) z/OS (MVS) WMI Event
Provider. It has an automation component. You could accomplish what you
want with a simple WTO in your Cobol programs.
"Kausar" <kausar.mohammad@gmail.com> wrote in message
news:d567f5b8.0410251031.7ddb663b@posting.google.com...
Hi,
In Host Initiated Processing scenario, we want to communicate from a
COBOL batch job [which is not CICS based ] to a .Net component. SNA
seems not to be an option for us here. The basic idea is: We want
business rules residing in a .Net component [using Biztalk Rules]
called from this COBOL batch job. Is there anyway i can achieve this?
Thanks in advance!
Kausar
|
|
|
| Back to top |
|
 |
Kausar
Guest
|
Posted:
Tue Oct 26, 2004 11:35 pm Post subject:
Re: Calling .Net component from COBOL batch job [Non-CICS] O |
|
|
Thanks Neil for the wide range of options you gave. SNA is not an option for
us for environmental reasons rather than anything else. The other two options
you mentioned are really interesting. I am also more inclined toward
messaging option. Are you aware of any Biztalk adapters offering this
functionality [ not using mqseries]. Thanks for your time.
- Kausar
"Neil Pike" wrote:
| Quote: | Kausar,
Several choices :-
1. APPC (SNA) which you say isn't an option, but not why. The Cobol program
would make an APPC connection to a program running on a server that listened on
APPC via a HIS server. With HIS2004 and Enterprise Extender this could all run
over IP.
2. TCP-IP sockets. Not sure if Cobol has built-in IP sockets stuff these
days - but if not an assembler module could act as an interface. Talking to a
program on the server that's listening on IP sockets.
Both the above involve some fairly low-level coding.
3. Use middle-ware. E.g. IBM MQ Series. Cobol (Mainframe) and Server
(C/VB/whatever) programs could communicate using MQ Series. Using this option
has a lot less low-level coding as all the comms/retry type stuff is handled by
MQ Series.
In Host Initiated Processing scenario, we want to communicate from a
COBOL batch job [which is not CICS based ] to a .Net component. SNA
seems not to be an option for us here. The basic idea is: We want
business rules residing in a .Net component [using Biztalk Rules]
called from this COBOL batch job. Is there anyway i can achieve this?
Thanks in advance!
Kausar
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)
|
|
|
| Back to top |
|
 |
Neil Pike
Guest
|
Posted:
Wed Oct 27, 2004 12:21 pm Post subject:
Re: Calling .Net component from COBOL batch job [Non-CICS] O |
|
|
Kausar,
I'm afraid I know not-a-lot about BizTalk, so couldn't tell you what it offered in
this situation. I doubt there would be anything, as MS's likely offering would be
MSMQ based, and, whilst that can "bridge" between MSMQ and MQSeries, it would only
remove the need for MQSeries on the server side - you'd still need it on the
mainframe side.
| Quote: | Thanks Neil for the wide range of options you gave. SNA is not an option for
us for environmental reasons rather than anything else. The other two options
you mentioned are really interesting. I am also more inclined toward
messaging option. Are you aware of any Biztalk adapters offering this
functionality [ not using mqseries]. Thanks for your time.
|
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise) |
|
| Back to top |
|
 |
|
|
|
|