IDMS

  • 1.  I ADS Alive and QREVIEW problem

    Posted May 09, 2017 03:37 PM

    I have a developer that is getting the following error message. When I go to QREVIEW it is empty. How do I get to the real details or prevent it from trying to go to QREVIEW so I can see the error on the screen. I tried going into ADSALIVE and it says I have to generate the dialog with Symbol Table in order to use it. Maybe that is why my QREVIEW is empty, but why would it go there if I don't have the symbol table?

     

    USG0071E DIALOG DPAS1020 V    1 ABENDED ERROR STATUS 0000 - DETAILS IN QREVIEW  

    V1  ENTER NEXT TASK CODE:      CA IDMS release 18.5 tape GJI50B node IDMSDCT

     

    Paul



  • 2.  Re: I ADS Alive and QREVIEW problem

    Posted May 11, 2017 03:07 PM

    Well after a lot of digging I found some abend details in the IDMS.PR00.SYSTEM.DDLDCLOG – this is actually an AREA, not a flat file -- SYSTEM.DDLDCLOG.

     

    This LOG is for ADSO program logging – shows errors/Aborts (ABRT), etc. This is NOT a transaction log for rollback/recovery. 

     

    I was able to report on this Log using PGM=IDMSBCF with this command:
    PRINT LOG FROM DATABASE MESSAGES STATISTICS TRACES DUMPS

    START AT '2017-05-11-08.00.00' STOP AT '2017-05-11-14.10.00.999999';

     

    Since this is an area in the SYSTEM Dictionary, I thinkk I should be able to look at it through DMLO but I can't figure out what the subschema is.



  • 3.  Re: I ADS Alive and QREVIEW problem

    Posted May 11, 2017 03:25 PM

    You can view the log online via the OLP task code. By default it takes you 30 minutes back into the log, but you can change the time/date on the top line to start at an earlier time. You can then scroll forward and back and hit Clear to exit. See the System Task and Operator commands guide for more details on using OLP.

    I think IDMSNWK9 is the subschema for the log area, but it would not be very easy finding what you want via DMLO. Much easier to use OLP or PRINT LOG.



  • 4.  Re: I ADS Alive and QREVIEW problem

    Posted May 17, 2017 03:44 PM

    That is exactly what I was looking for. I dug around in OLP and found that the problem was in another program and after a few S0C4 abends IDMS disabled the program for any further executions. After a bit more digging I found out a newcopy would bring the program back in, but by then I had had a weekly IPL and the app was working fine.