RE: MIDRANGE-L Digest V3 #671

Was this one of the next number tables, F0002 or F00021 or F00022?

There is no reason (except performance, the reason nearest to my heart) to
avoid journaling JDE control files.  I realize that this is pouring salt on
the wound but better to address the issue before it vanishes the second time
than to wait for it to vanish the third time.

If the table isn't journaled, is it mirrored to another system with Data
Propagator?

Are you using the object duplication software from Lakeview or Vision
Solutions?

If the users are on TSE servers, check the JDE.logs or debug logs if they
are running.  You never know what you might find.

If you are coexistant, check interactive job logs.  If you have active
developers, check all the job logs.

As someone else pointed out, the audit journal is a very good idea.

You might look in the system operator message queue.  Once again, you never
know what you will find.

If you save job logs for QZDASOINIT jobs, you might scan them all for the
file name.

You might also look in the VMC logs.  If the table vanish from an OS/400
issue, it might have been recorded in there.  STRSST, start a service
function, display microcode log, display, put in the time range and press
enter.  You never know.

Of course, you have looked in QRECOVERY and QRCL, right?

I'm out of ideas ... for now.

Short story.  A long time ago, there was a guy working at JDE in the
financial analysis department.  He decided that something had to go so he
typed in "dltpgm x*" or something like that.  This was on the primary
production system at JDE called JDEC.  A few milliseconds later, about 1,500
users suddenly dropped off the face of the earth .  And a few milliseconds
after that, his QSECOFR-class password became a QUSER class password.  It
happens, even when you try not to do it.  By the way, it wasn't me.  Yes,
I'm stunned too.  I know who it was but I haven't seen him in a while - he
will NEVER live this down :)


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 prumschlag@phdinc.com
Sent: Tuesday, September 05, 2000 4:22 PM
To: MIDRANGE-L@midrange.com
Subject: Re: MIDRANGE-L Digest V3 #671




Hi, all.  I am looking for some help.

Two files (one physical and one logical) have disappeared from our system
today.
They are JD Edwards control files that are referenced often by programs all
over
the system.  Based on the timing of jobs completing successfully and jobs
blowing up with File Not Found errors, we have narrowed the time slot down
to
somewhere between 13:55 and 13:58.  We would like to know how this has
happened
so we can prevent it from happening again.

We figure the choices are 1)  Someone deleted them either intentionally or
unintentionally, 2)  JD Edwards programs messed up, or 3)  OS/400 lost the
files.  We are pursuing 1 and 2, but no one here will 'fess up and JDE
swears
that there is no function in the system that would delete these files.  I
don't
want to blame the AS/400, but I have to at least consider the possibility.
Is
anyone aware of any system records that would help us trace this?  The
system
log does not have that kind of detail,  and because this is a JDE control
file
it is kept in a library that is not journaled.

Much obliged.

Phil


+---
| 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
+---