3/14/08 Easy way to remove job schedule entries with one command.

Use the following command:

RMVJOBSCDE *ALL

Or wildcard RMVJOBSCDE XXX*

**CORRECTION**
RMVJOBSCHE *ALL is NOT valid. This was an oversight during the verification process. However the generic version (RMVJOBSCDE XXX*) does work, and will work better if the parameter ENTRYNBR(*ALL) is added to the command as follows: -

RMVJOBSCHE JOB(A*) ENTRYNBR(*ALL)

This command is valid on the following i5/OS environments: V4R5M0, V5R1M0, V5R2M0 and V5R3M0. It has not yet been verified for V6R1M0.


Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation.

5 comments:

Jim said...

Is there a version of the OS that this works on? I've tried this and it doesn't work!

Vision Solutions said...

There was a typo in the command. In the example of the wildcard command, it showed "RMMVJOBSCDE", it should be "RMVJOBSCDE". Please try this and advise if you still have problems. Sorry for the error.

Jim said...

I recognized the the misspelling the first time. As far as I can tell, this command does NOT work to clear all job schdule entries.

Vision Solutions said...

The Vision technician who submitted this tip has been advised and a response should be forthcoming.

Vision Solutions said...

You are correct, Jim. "RMVJOBSCHE *ALL" is not valid. Unfortunately, we didn’t pick this up during the verification process.

However the generic version does work, and will work better if the parameter ‘ENTRYNBR(*ALL)’ is added to the command as follows: -

RMVJOBSCHE JOB(A*) ENTRYNBR(*ALL)

This has been verified on a V4R5M0, V5R1M0, V5R2M0 and V5R3M0 machines and it is the same for all. This has not yet been verified on a V6R1M0 machine.

The above change has been made to the original blog entry.

Thank you for bringing this to our attention, Jim.