none
SNA Application issues with HIS 2009 Server/Client RRS feed

  • Question

  • Hi All,

           We are upgrading our HIS infrastructure from 2000 to 2009 version. I am facing an issue with one of the SNA applications when using HIS 2009 infrastructure.

           The Application is a Web service. The application is setup as a COM service in a server and served to users using IIS. The COM service makes use of SNA client to connect to the HIS server which connects to the Mainframe host. The SNA client is running as a service under a domain service account.

           I do not see the application making use of TI (Transaction Integrator) as there is no such configuration in the HIS 2000 servers.

           The HIS 2000 infrastructure has all the feautures installed but only the SNA server component is configured. The HIS 2009 infrastrucure has only the SNA server component installed.

          I have performed testing for various configurations.

          1) HIS 2000 client pointing to HIS 2000 servers - Application works no stability issues.

          2) HIS 2000 client pointing to HIS 2009 server - Application works, but there are stability issues.

          3) HIS 2009 client pointing to HIS 2000 servers - Application works no stability issues.

          4) HIS 2009 client pointing to HIS 2009 server - Application works, but there are stability issues.

          The application works on that day, but starts giving the following error on the next day morning (1009: Mainframe communication failed on ReceiveData).

          Also, simply restarting the SNA service is not solving the issue. The application stars working when I unconfigure the client and configure it to point to the HIS 2000 servers. Then when I unconfigure the client and configure it to point to the HIS 2009 server, it starts working.

          Kinldy let me know if you need more information to help me solve this issue.

          Thanks in advance.

    Regards,

    Kumaran Ravichandran.



    Wednesday, May 11, 2011 7:25 AM

Answers

  • Kumaran,

    The error indiactes that the userid and/or password that wasa sent to the mainframe application was invalid. The RECEIVE_AND_WAIT completes with the following return codes:

    Primary RC = 0003 (AP_ALLOCATION_ERROR) 
    Secondary RC = 080F6051 (AP_SECURITY_NOT_VALID)

    You can also see this in the Client Message trace where the data returned from the mainframe indicates that the "a security violation was detected".

     

    If you have the portion of the API trace where the ALLOCATE is shown, it will have the userid and password that was sent to the mainframe.

     

    Thanks...

     

     


    Stephen Jackson - MSFT
    Tuesday, May 17, 2011 3:34 PM

All replies

  • Kumaran,

    It might help if you include the exact event or error message that occurs. Is there more details about the 1009 error? Where is this returned (on the HIS Client system)? This almost looks like an application specific error and not a HIS specific error.

    Do you have any more details on the application? Is it an APPC/CPI-C application that uses LU 6.2 sessions on the back end HIS Server?

    Are there any events being logged on the HIS Server whent his occurs or any other HIS events logged on the HIS Client system?

    Thanks...


    Stephen Jackson - MSFT
    Thursday, May 12, 2011 4:42 PM
  • Stephen,

               The error message is provided by the application. There are no details provided on this error by the application. It seems the application let the HIS takes care of SNA related error messages.

               I could not find specific error messages in the HIS server at the point of occurence of this error message. Should I enable SNA tracing to find error details on the HIS client side?

               I have updated the original post to point out that the stability issue is not occuring in one more scenario. At this point, it looks like an issue with the configuration of the HIS 2009 server.

               I will source more information on the application and will provide it in the next post.

    Regards,

    Kumaran R.

    Friday, May 13, 2011 1:22 AM
  • Stephen,

               This is an APPC/CPI-C application that uses LU 6.2 sessions on the back end HIS server.

               I have update the original post to show that there is instability when using the HIS 2009 server.

               This is working fine with the HIS 2000 server. It works with the HIS 2009 server, but with stability issues.

               The HIS 2000 and 2009 servers are setup mostly alike, except that I am not using all the feautures in the HIS 2009 server. I am only using the basic SNA server function.

               I will try some more testing and will post the information here.

    Regards,

    Kumaran R.

    Monday, May 16, 2011 12:00 AM
  • It will likely take some HIS traces (SNA Application on the HIS client and SnaServer on the HIS Server) in order to see what is going on at the time the application returns the error.

    Thanks...


    Stephen Jackson - MSFT
    Monday, May 16, 2011 4:26 PM
  • Stephen,

                 I did setup SNA traces on the HIS client and HIS server end.

                 The excerpts from the Trace files when the error occurs are as follows.

                 HIS Client:

                 From File CLIAPI1.ATF

    Custom     17/05/2011   09:17:23.220  CPIC CMRCV request                                         3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC  Conversation ID = 05000000                                  3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC  Requested length = 16438                                   3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC Conversation characteristics                                  3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC  Conversation type = CM_MAPPED_CONVERSATION                          3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC  Fill type = CM_FILL_LL                                    3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.220  CPIC  Receive type = CM_RECEIVE_AND_WAIT                              3704      4580      271       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC --------------------------------------------------------------------------------        3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC MC_RECEIVE_AND_WAIT request                                  3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC                                                 3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC Type:Sync                 VerbID:00034004                   3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC                                                 3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC ---- Verb Parameter Block at address 061A0000 ----                       3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC 0B000100 00000000 00000000 00000000   <................>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC 38594F03 58654F03 00000101 00003640   <8YO.XeO.......6@>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.220  APPC 00000000 0033A502 00000000 00000000   <.....3v.........>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC --------------------------------------------------------------------------------        3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC MC_RECEIVE_AND_WAIT response, result = ALLOCATION_ERROR                    3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC                                                 3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC Type:Sync                 VerbID:00034004                   3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC                                                 3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC ---- Verb Parameter Block at address 061A0000 ----                       3704      4580      268       com_trc_line  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC 0B000100 00030000 080F6051 00000000   <..........`Q....>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC 38594F03 58654F03 00040101 00003640   <8YO.XeO.......6@>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Unknown Trace Condition17/05/2011   09:17:23.345  APPC 00000000 0033A502 00000000 00000000   <.....3v.........>                   3704      4580      166       com_trc_dumpl  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC --------------------------------------------------------------------------------        3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC CMRCV response, result = CM_SECURITY_NOT_VALID                         3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC  Buffer empty                                         3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC  Data received type = CM_INCOMPLETE_DATA_RECEIVED                       3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC  Received length = 0                                      3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC  Status received = CM_NO_STATUS_RECEIVED                            3704      4580      271       com_trc_line  semftrci.c   0        
    Custom     17/05/2011   09:17:23.345  CPIC  Request to send received = CM_REQ_TO_SEND_NOT_RECEIVED                    3704      4580      271       com_trc_line  semftrci.c   0        
    
    

                       From file CLIMSG1.ATF

    Recoverable   17/05/2011   09:17:23.345  PVI  040202B2->12000005 LU 6.2                                   3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI           MSGID:RDAT  MSGTYP:DALFL                          3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI                                                 3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  ---- Header at address 03FC4174, 1 elements ----                        3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  01040000 00002E00 021C0000 0100D815   <..............Q.>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI                                                 3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  ---- Element at address 04046910, start 20, end 181 ----                    3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  00A212E1 00260310 F3151104 120041F5   <.s...&..3.....A5>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  F6F5F5D4 F1F54040 40C1D9F1 F9400603   <655M15@@@AR19@..>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  F0F6F5F0 060FC3C9 C3E20078 C4C6C8C1   <0650..CICS.xDFHA>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  C3F2F0F4 F740F1F7 61F0F561 F2F0F1F1   <C2047@17a05a2011>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  40F0F97A F1F77AF2 F340E2E3 F1F9C3C9   <@09z17z23@XXXXXX>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  C3E240E6 88899385 40978599 86969994   <XX@While@perform>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  89958740 81954081 A3A38183 88408696   <ing@an@attach@fo>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  99409596 848540D1 D3C2E6D7 C1C4C440   <r@node@XXXXXXXX@>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  8140A285 83A49989 A3A840A5 89969381   <a@security@viola>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  A3899695 40A681A2 408485A3 8583A385   <tion@was@detecte>                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  844B                  <dK       >                   3704      5416      191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  --------------------------------------------------------------------------------        3704      5416      293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.345  PVI  040202B2->12000005 LU 6.2                                   3704      5416      293       com_trc_line  semftrci.c   0        
    
    

                     HIS Server:

                     From file SNAServr_MSG1.ATF

    Recoverable   17/05/2011   09:17:23.310  PVI  010202B2->12000005 LU 6.2                                   6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI           MSGID:RDAT  MSGTYP:DALFL                          6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI                                                 6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  ---- Header at address 011E6FE8, 1 elements ----                        6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  01040000 00002E00 021C0000 0100D815   <..............Q.>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI                                                 6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  ---- Element at address 01C32904, start 20, end 181 ----                    6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  00A212E1 00260310 F3151104 120041F5   <.s...&..3.....A5>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  F6F5F5D4 F1F54040 40C1D9F1 F9400603   <655M15@@@AR19@..>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  F0F6F5F0 060FC3C9 C3E20078 C4C6C8C1   <0650..CICS.xDFHA>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  C3F2F0F4 F740F1F7 61F0F561 F2F0F1F1   <C2047@17a05a2011>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  40F0F97A F1F77AF2 F340E2E3 F1F9C3C9   <@09z17z23@ST19CI>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  C3E240E6 88899385 40978599 86969994   <CS@While@perform>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  89958740 81954081 A3A38183 88408696   <ing@an@attach@fo>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  99409596 848540D1 D3C2E6D7 C1C4C440   <r@node@XXXXXXXX@>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  8140A285 83A49989 A3A840A5 89969381   <a@security@viola>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  A3899695 40A681A2 408485A3 8583A385   <tion@was@detecte>                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  844B                  <dK       >                   6044      652       191       com_trc_dumpl  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  --------------------------------------------------------------------------------        6044      652       293       com_trc_line  semftrci.c   0        
    Recoverable   17/05/2011   09:17:23.310  PVI  010202B2->12000005 LU 6.2                                   6044      652       293       com_trc_line  semftrci.c   0        
    
    

                       The trace files on both the client and the server are pointing to some security violation. Is this occuring due to configuration of HIS client/server or some access permission setting in the Mainframe host? Kindly help me to solve this issue.

                       There is no attachment option in the forum.

                       Kindly let me know if you need the complete informaton from the Trace files.

    Regards,

    Kumaran Ravichandran

     

    Tuesday, May 17, 2011 1:36 AM
  • Kumaran,

    The error indiactes that the userid and/or password that wasa sent to the mainframe application was invalid. The RECEIVE_AND_WAIT completes with the following return codes:

    Primary RC = 0003 (AP_ALLOCATION_ERROR) 
    Secondary RC = 080F6051 (AP_SECURITY_NOT_VALID)

    You can also see this in the Client Message trace where the data returned from the mainframe indicates that the "a security violation was detected".

     

    If you have the portion of the API trace where the ALLOCATE is shown, it will have the userid and password that was sent to the mainframe.

     

    Thanks...

     

     


    Stephen Jackson - MSFT
    Tuesday, May 17, 2011 3:34 PM
  • Stephen,

                The User ID and password were fine.

                In our organisation, we have security controls imposed on Functional logon IDs. These applications were non-interactive applications and hence were using Functional Logon ID. The restrictions were placed on the source based on the APPC LU names.

                New PUs were created and hence new LU names for this upgrade project as I wanted to run them in parallel with the old infrastructure for fallback purposes and have least impact on Production systems. The new LU names were added to the source restrictions in the Test environment.

                The applications are working fine in the test environment now.

                Thank you for all the help.

    Regards,

    Kumaran Ravichandran

    Friday, May 27, 2011 12:53 AM
  • Kumaran,

    It might help if you include the exact event or error message that occurs. Is there more details about the 1009 error? Where is this returned (on the HIS Client system)? This almost looks like an application specific error and not a HIS specific error.

    Do you have any more details on the application? Is it an APPC/CPI-C application that uses LU 6.2 sessions on the back end HIS Server?

    Are there any events being logged on the HIS Server whent his occurs or any other HIS events logged on the HIS Client system?

    Thanks...

    Mr dich thuat


    http://www.dichcongchung.org
    Tuesday, June 7, 2011 4:04 AM