RE: Did you ever see this message & what do you think,

One or more of the following:

1. someone did some very bad coding
2. you need one or more IBM PTFs
3. Something bad happened sometime ago, and you haven't fixed it yet.

What is this file for?  Who put it there?  Why is everyone opening it?
Library PACONVFIL sounds like some company named PA and convert file or
convert files.  File BSRTSWK sounds like some kind of work file.  Member *N
is probably the first member.  What is up with all that?

To further check out item 3, STRSST, display VMC log, select major code
0300.  That will display all of the "new damage detected" events starting
with the last one at the bottom of the screen.  If you use major code 0301,
it will show all of the "previously detected damage detected again" events.

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of
ORiordan_Paudie@emc.com
Sent: Tuesday, August 22, 2000 12:23 PM
To: MIDRANGE-L@midrange.com
Subject: Did you ever see this message & what do you think,


hi All
I have to kick interacive users off the system as they are locking this file
etc
before it comes usable again, and I have alot of interactive users locking
this file amoungst others


 Message ID . . . . . . :   CPF3245       Severity . . . . . . . :   40

 Message type . . . . . :   Diagnostic

 Date sent  . . . . . . :   22/08/00      Time sent  . . . . . . :
19:14:07


 Message . . . . :   Damage to file BCRTSWK member *N prevents operation on

   file BCRTSWK.

 Cause . . . . . :   The operation that was tried on file BCRTSWK in library

   PACONVFIL was prevented because another operation against file BCRTSWK

   member *N was in progress when a previous job was interrupted, causing

   logical damage to file BCRTSWK member *N in library PACONVFIL.  The
previous
   operation type code is 8.

 Recovery  . . . :   The file may be usable after the next IPL or after the

   same type of operation is tried again on the damaged file BCRTSWK. If the

   previous operation was type 34, retry the prevented operation.
Otherwise,
   retry the previous operation. If either the IPL fails or the operation
fails
   when it is tried again, the damage cannot be repaired.  However, the data
in
the file may be accessible. The operation type codes and their meanings

follow:

   1 -- RNMOBJ.

   2 -- MOVOBJ.

   3 -- GRTOBJAUT.

   4 -- RVKOBJAUT.

   5 -- CHGOBJOWN.

   6 -- DLTF.

   7 -- CRTPF, CRTLF or CRTSRCPF.

   8 -- RMVM.

   9 -- ADDPFM or ADDLFM.

  10 -- Restore operation.

  11 -- Journal operation.  Recovery can only be attempted at IPL.
  12 -- File conversion operation.  This operation cannot be recovered.
  13 -- CHGPF, CHGLF, or CHGSRCPF.
  14 -- RNMM.
  16 -- Journaled file conversion.  Recovery can only be attempted at IPL.
  17 -- Query operation.
  18 -- Restore of a data dictionary.
  19 -- Change file operation.
  21 -- Rename library operation.
  22 -- Save operation.
  34 -- Create of a S/36 work file.
  43 -- Add physical file constraint.
  44 -- Remove physical file constraint.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---