Cobol Error... - Hewlett Packard

This is a discussion on Cobol Error... - Hewlett Packard ; Hi all, Last night, one of our production jobs blew up with an ugly error.. This is an Amisys job and has been running fine all along from several years, and never run into this situation before. Anybody got any ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Cobol Error...

  1. Cobol Error...

    Hi all,

    Last night, one of our production jobs blew up with an ugly error.. This is an Amisys job and has been running fine all along from several years, and never run into this situation before. Anybody got any idea what happened here ? We have already notified HP and will likely be notifying Amisys owner DST about this sometime tomorrow.



    607 :RUN BCP0100.PROGXL.!HPACCOUNT;XL="!QXLINFO";NMSTACK=1300000
    608
    609
    610 ** BCP0100 VERSION 11.01.08.04 02/27/2004 01:02 AM **
    611 ** Copyright AMISYS, LLC **
    612 ** 1990-2003 All Rights Reserved **
    613
    614
    615 Enter the Mode : 1
    616
    617 Enter the Batch/Operator : @
    618
    619 Enter the Claim Type : @
    620
    621 Enter the Effective Date : 19000101
    622
    623 Enter the End date : 99991231
    624
    625 Enter the Action Trigger :
    626
    627 Enter the User Op# : *SYS
    628
    629 Enter the Load EX-Code flag: N
    630 *** FATAL IMAGE ERROR ******
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    631 ...GQC....B......
    632 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    633 ****************************
    634 *** FATAL IMAGE ERROR ******
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    635 ...GQC....B......
    636 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    637 ****************************
    638 *** FATAL IMAGE ERROR ******
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    639 ...GQC....B......
    640 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    641 ****************************
    642 *** FATAL IMAGE ERROR ******
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    643 ...GQC....B......
    644 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    645 ****************************
    646 Filename: PR0004M
    647 File status is 9G
    648 **** COBerr 644 Unable to open file, See File System error
    649 Program file: BCP0100.PROGXL.AMISYS
    650 TOO MANY FILES OPEN (FSERR 71)
    651
    652 +-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
    653 ! ERROR NUMBER: 71 RESIDUE: 18003 (WORDS) !
    654 ! BLOCK NUMBER: 538976288 NUMREC: 17746 !
    655 +------------------------------------------------+
    656 **** COB_QUIT 644 ****
    657
    658 ABORT: BCP0100.PROGXL.AMISYS
    659 NM SYS a.00fdbf70 dbg_abort_trace+$28
    660 NM USER 14d.0026b398 COB_QUIT+$b8
    661 NM PUB 322.01381378 cls0120$001$+$55bc
    662 NM PROG 254.0005c50c bcp0100$004$+$32b8
    663
    664 RUN BCP0100.PROGXL.AMISYS;XL="XL.PUB.AMISYS,XL.OW.DISC3,xl0804f3.pub.hss,PHLIBXL S.PH839C.COGNOS,XLOMNIDX.PUB.SYS,ST2XL.PU
    665 LAMISYS.PUB.SYS";NMSTACK=1300000
    666 Program terminated in an error state. (CIERR 976)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    667 :


    Thanks
    > Raghu Rao
    >


    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  2. Re: Cobol Error...

    Thanks to all those who replied at a lightning pace (over the weekend) when we really needed it..

    It turns out........ It was not a Cobol Error. It was not a File Error. It was not a IMAGE error. It was not a System Error.. All of these threw up because of something else..

    It took tech brains nearly 6-8 hours to debug and fix the issue. The Program was trying to price the claim from an external HSS application over awindows server and the connection to that server failed (because of a patch upgrade followed by the a communicator instance not starting properlyon that windows box), so it rolled over to a 2nd instance of that serveras backup and that could not handle our full production load. The 1st instance kept the connection open till the parent calling process completedand the 2nd instance opened a new connection every time a claim called the pricing routine. The 2nd instance kept returning back correct pricing results upto certain time and then it just froze because the connection limit was hit. Nothing related to other network connectivity (including FTP) on the production box was working because there were all dead sessionsall over the box. Finally after fixing the HSS issue, we were able to clear all those dead sessions and get everything back to normal.

    Hope this does not happen to other Amisys clients.

    Thanks again
    Raghu Rao.

    > _____________________________________________
    > From: Rao, Raghu
    > Sent: Sunday, November 09, 2008 5:41 PM
    > To: 'HP3000-L@RAVEN.UTC.EDU'
    > Subject: Cobol Error...
    >
    > Hi all,
    >
    > Last night, one of our production jobs blew up with an ugly error.. This is an Amisys job and has been running fine all along from several years, and never run into this situation before. Anybody got any idea what happened here ? We have already notified HP and will likely be notifying Amisys owner DST about this sometime tomorrow.
    >
    >
    >
    > 607 :RUN BCP0100.PROGXL.!HPACCOUNT;XL="!QXLINFO";NMSTACK=1300000
    > 608
    > 609
    > 610 ** BCP0100 VERSION 11.01.08.04 02/27/2004 01:02 AM **
    > 611 ** Copyright AMISYS, LLC **
    > 612 ** 1990-2003 All Rights Reserved **
    > 613
    > 614
    > 615 Enter the Mode : 1
    > 616
    > 617 Enter the Batch/Operator : @
    > 618
    > 619 Enter the Claim Type : @
    > 620
    > 621 Enter the Effective Date : 19000101
    > 622
    > 623 Enter the End date : 99991231
    > 624
    > 625 Enter the Action Trigger :
    > 626
    > 627 Enter the User Op# : *SYS
    > 628
    > 629 Enter the Load EX-Code flag: N
    > 630 *** FATAL IMAGE ERROR ******
    > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 631 ...GQC....B......
    > 632 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    > 633 ****************************
    > 634 *** FATAL IMAGE ERROR ******
    > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 635 ...GQC....B......
    > 636 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    > 637 ****************************
    > 638 *** FATAL IMAGE ERROR ******
    > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 639 ...GQC....B......
    > 640 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    > 641 ****************************
    > 642 *** FATAL IMAGE ERROR ******
    > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 643 ...GQC....B......
    > 644 01-01 Can't Open TICAT000.PUB.SYS ......d.........B.
    > 645 ****************************
    > 646 Filename: PR0004M
    > 647 File status is 9G
    > 648 **** COBerr 644 Unable to open file, See File System error
    > 649 Program file: BCP0100.PROGXL.AMISYS
    > 650 TOO MANY FILES OPEN (FSERR 71)
    > 651
    > 652 +-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+>
    > 653 ! ERROR NUMBER: 71 RESIDUE: 18003 (WORDS) !
    > 654 ! BLOCK NUMBER: 538976288 NUMREC: 17746 !
    > 655 +------------------------------------------------+
    > 656 **** COB_QUIT 644 ****
    > 657
    > 658 ABORT: BCP0100.PROGXL.AMISYS
    > 659 NM SYS a.00fdbf70 dbg_abort_trace+$28
    > 660 NM USER 14d.0026b398 COB_QUIT+$b8
    > 661 NM PUB 322.01381378 cls0120$001$+$55bc
    > 662 NM PROG 254.0005c50c bcp0100$004$+$32b8
    > 663
    > 664 RUN BCP0100.PROGXL.AMISYS;XL="XL.PUB.AMISYS,XL.OW.DISC3,xl0804f3.pub.hss,PHLIBXL S.PH839C.COGNOS,XLOMNIDX.PUB.SYS,ST2XL.PU
    > 665 LAMISYS.PUB.SYS";NMSTACK=1300000
    > 666 Program terminated in an error state. (CIERR 976)
    > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > 667 :
    >
    >
    > Thanks
    > Raghu Rao
    >



    ********************************************
    This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the individual or the entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any use, dissemination, or copying of this communication is prohibited by federal law. If you have received this communication in error, please destroy it and notify the sender.
    ********************************************

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


+ Reply to Thread