RE: MONMSG CPF2103 but still "unmonitored", causing halt

It's been a while since I did anything like that in CL but I think what
you have to do is walk backwards through the job log looking for the
CPF2102.  I believe it will show up as a *DIAG message and should be one
or two before the error triggering your MONMSG.  Try RCVMSG with a
message type of *PRV.

Rick

> -----Original Message-----
> From: G Armour [mailto:garmour400m@xxxxxxxxx]
> Sent: Tuesday, October 21, 2003 1:39 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: MONMSG CPF2103 but still "unmonitored", causing halt
> 
> 
> Well, *how* would I detect this particular problem?  I have 
> since replaced
> the CPF2102 with a MONMSG CPF9999 after the others.  It 
> appears that the
> CPF9999 message tattles on the CPF2102.  Can I interrogate the CPF9999
> message to make sure that it was caused by CPF2102?
> 
> TIA, GA
> 
> --- "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:
> > Message CPF2102 is not monitorable from DSPPGMREF.  Prompt 
> the command,
> > move the cursor to the heading and press F1.  Scroll down 
> until you see
> > the monitorable error messages.
> > 
> > The CPF3033 and CPF3034 messages are monitorable however.  
> That makes me
> > think what you are seeing is the expected behavior.  
> CPF2102 is caught
> > by the IBM program which then issues a message monitorable 
> by your CL.
> > 
> > HTH,
> > 
> > Rick
> > 
> > 
> > > -----Original Message-----
> > > From: G Armour [mailto:garmour400m@xxxxxxxxx]
> > > Sent: Tuesday, October 21, 2003 11:13 AM
> > > To: midrange-l@xxxxxxxxxxxx
> > > Subject: MONMSG CPF2103 but still "unmonitored", causing halt
> > > 
> > > 
> > > Never seen this one before.  Performing DSPPGMREF on program 
> > > objects to an
> > > outfile and getting CPF2103 on several objects in the system. 
> > >  The program
> > > objects appear to be undamaged; the few I've checked are old, user
> > > application, CL programs.  One I looked at via DSPOBJD has no 
> > > values for
> > > "Created by user" and "System created on", but it is an 
> object that is
> > > being used, apparently with no execution errors.  This may be 
> > > a clue:  It
> > > was compiled at V1R2M0 and can run on V1R1M0.  Further 
> > > testing shows that
> > > all of the several objects that cause this error have a 
> > > system version of
> > > V1R2M0 or V1R3M0.  However, note that there are hundreds of 
> > > such objects
> > > on the system that do NOT cause the error.  Here is the 
> test code I'm
> > > running that duplicates the problem:
> > > 
> > >    DspPgmRef  Pgm( CUSWW/WWEPG1* ) Output( *OutFile ) +
> > >                 ObjType( *PGM ) +
> > >                 OutFile( GBAlibSysF/$DspPgmRfO ) +  
> > >                 OutMbr( *First *Add )
> > >      MonMsg     CPF2102  /* Invalid Object Type */ 
> > >      MonMsg     CPF3034  /* Object cannot be displayed (locked) */
> > >      MonMsg     CPF3033  /* Object no longer exists */
> > > 
> > > Even though I am monitoring for CPF2102, I'm still getting an 
> > > exception
> > > requiring a response, being told that CPF2102 is unmonitored:
> > > 
> > >     1100 - DSPPGMREF PGM(CUSWW/WWEPG1*) OUTPUT(*OUTFILE) 
> OBJTYPE(*PGM)
> > >     OUTFILE(GBALIBSYSF/$DSPPGMRFO) OUTMBR(*FIRST *ADD)        
> > >            
> > >   Object type and subtype code 'C740'X not valid.             
> > >            
> > >   15 records added to member $DSPPGMRFO in file $DSPPGMRFO in 
> > > GBALIBSYSF.
> > >   Function check. CPF2102 unmonitored by QWHDSPPR at 
> > > statement *N,       
> > >     instruction X'0212'.                                      
> > >            
> > >   CPF9999 received by DSPPGRFOBZ at 1100. (C D I R)           
> > >            
> > > 
> > > (The first message, with the 'C740'X, is the CPF2102 
> > > message.)  The one
> > > thing that caught my eye is that function check message 
> is saying that
> > > CPF2102 is unmonitored by ***QWHDSPPR***, and not by my 
> > > program.  Is that
> > > the expected behavior?
> > > 
> > > TIA, GA