Skip to main content

Hello,

does anybody has a sample for MF replacement of IBM CICS TG?

With IBM  CICS TG there are in folder samples some cobol sources (ec01.cbl, ec02.cbl abd ec03.cbl for host side) and ecib1.cbl as sample client program.

I don't find in help the steps to change ecib1.cbl from IBM TG ECI to proprietary support for ECI.

If I understand properly,

  • I have to set at the compile directives INITCALL(casbnccl) to adress the CICSEXTRENALCALL,
  • I can't use CICSECILISTSYSTEMS
  • I muts put in ECI-SERVER variable  in the ECI parameter block the  host:port adress of host:webListenerPort

In standard ECI copy deleivered with IBM CICS TG there is no ECI-SERVER field.

I would like to be simulate server selection like with CICSECILISTSYSTEMS because the in real application the user can select the target host/server  

Thank in advance

Regards

Vladimir

 

 

 


#EnterpriseDeveloper

Hello,

does anybody has a sample for MF replacement of IBM CICS TG?

With IBM  CICS TG there are in folder samples some cobol sources (ec01.cbl, ec02.cbl abd ec03.cbl for host side) and ecib1.cbl as sample client program.

I don't find in help the steps to change ecib1.cbl from IBM TG ECI to proprietary support for ECI.

If I understand properly,

  • I have to set at the compile directives INITCALL(casbnccl) to adress the CICSEXTRENALCALL,
  • I can't use CICSECILISTSYSTEMS
  • I muts put in ECI-SERVER variable  in the ECI parameter block the  host:port adress of host:webListenerPort

In standard ECI copy deleivered with IBM CICS TG there is no ECI-SERVER field.

I would like to be simulate server selection like with CICSECILISTSYSTEMS because the in real application the user can select the target host/server  

Thank in advance

Regards

Vladimir

 

 

 


#EnterpriseDeveloper

Hello,

 

I managed to start communication between client and server using Micro Focus proprietary support for ECI.

The short notes in documentation are not so useful, but testing I found “how to”.

The “standard” ECI interface looks like

      *

      * Issue a CICS_Externalcall for an ECI_SYNC                  

      *

 

           MOVE LOW-VALUES TO ECI-PARMS

 

           SET  ECI-SYNC            TO TRUE

           MOVE 'EC01'              TO ECI-PROGRAM-NAME

           MOVE USERID              TO ECI-USERID

           MOVE PASSWD              TO ECI-PASSWORD

           MOVE SERVER              TO ECI-SYSTEM-NAME

           SET  ECI-COMMAREA        TO ADDRESS OF COMMAREA

           MOVE LENGTH OF COMMAREA  TO ECI-COMMAREA-LENGTH

           MOVE 0                   TO ECI-TIMEOUT

           SET  ECI-NO-EXTEND       TO TRUE

           SET  ECI-VERSION-1A      TO TRUE

 

I am using external

set ES_ECI_SOCKET=localhost:5550 addressing system to reach the region, therefore the ECI-SYSTEM-NAME is not used.

Other solution with

Set ES_ECI_CCITCP2=localhost:86

usesECI-SYSTEM-NAMEto address the region from MFDS repository

 

Proposal to development:

To be consistent with IBM TG style and make easier the migration, instead of using mf-client.dat pointing to one MFDS, try to implement let call it

 

mf-host.dat having entries

------------------------------------------------------------------------

;

; The [directories] section lists directories for service resolution

;

 

[directories]

; Point MFCC to local MFDS

mrpi://127.0.0.1:86

[Regions]

REGIONP=//123.45.678.90;1234

REGIONT=//123.45.678.91:4321

 

;

; The [tracing] section enables MFCC tracing; higher numbers log more

; information.

;

 

[tracing]

level=0

-----------------------------------------------------

and than use

MOVE ‘REGIONP’              TO ECI-SYSTEM-NAME

 

Regards

Vladimir