Procedure to shutdown JDE v7.3

Looking for process to shutdown the as400/JDE system.

Are you wanting to shut it down so no one can sign on in JDE?
Or what are you trying to accomplish?

Jim

Re: RE: Procedure to shutdown JDE v7.3

PWRDWNSYS(*IMMED) and walk away...

If you just want to "disable" JDE from being able to log into, rename a library like JDFOBJ to something else and that will certainly stop anyone from logging in!

Hello short of power down. Ending subsystem Qinter works , we do this during nightly backups. This gives us a small window of time, as people are here all night and they will jump on if allowed. You will need to build a cl to do this or do it from a workstation in the qctl subsystem
Fred 7.3 cum 13

Just one thing to remember with the PWRDWNSYS command - don't forget the Restart option. If left at the default *NO, a manual restart will be needed.

Cheers

Well since the original poster is not responding then I will give my
suggestion, since everyone else.

Doing the power down will not let anyone get onto the system period,
except for someone on the system console or to a device defined in QCTL.
But even at that a user could still get into JDE.

What we do here is we rename the J98INITA object in JDFOBJ to
J98INITAXX. Then we
changed our user profiles to use this newly named object, so we can
still get on into JDE. Then when we are done we rename the object back
and then change our profiles back.

I guess the thing I need to know from rkowals, is what they are trying
to accomplish or why they want to keep users out of JDE.

Jim Rubino

"What we do here is we rename the J98INITA object in JDFOBJ to
J98INITAXX. Then we changed our user profiles to use this newly named
object, so we can still get on into JDE. Then when we are done we rename
the object back and then change our profiles back."

I've used a similar technique but it doesn't involve changing the
profiles and avoids making the system look broken. Rename J98INITA as
Jim does. Then have another CL program that gets renamed to J98INITA.
The new program displays a pretty screen format with the blurb about
the downtime and all the 'have a nice day' stuff. It also has a single
unlabelled non-display input field.

Once the programs are renamed issue messages to all active users and
shut down QINTER (controlled and with a generous time limit) then
restart it.

After receiving the input from the display format the program checks
to see if the input matches a hard-coded password. If it does it calls
the renamed J98INITA otherwise it signs the user off. This keeps the
riff-raff ^h^h^h^h^h^h^h^h^h your valued customers out of the system
while retaining a polished appearance. When you're ready to let them
back in just rename both programs back to their original names.

We have our users interactive jobs set up to run in Qinter and our IT dept interactive jobs set to run in jobq ITdept. Then if we what to keep users out we shut down Qinter and leave ITdept running. Once we are done with what needed to be done, we restart Qinter.

The original post was so vague and so naive, I think we can safely assume the author knows precious little about JDE and the AS400.

Given that, I'm wondering if providing details on how to power off the AS400 is even a good idea - based on the old idea that a little knowledge can be dangerous...

It seems we are going through another phase of people posting on the wrong boards and with questions they should be able to get answers to from withn their own company. If they can't - it diesn't inspire a lot of confidence...