How to find parameters for validity checker program for OS400 commands or how to cancel the command processing program if you are in command exit program used with QIBM_QCA_RTV_COMMAND and QIBM_QCA_CHG_COMMAND

pts.
Tags:
AS/400
RPG
My problem is restrict UPDDTA command for specific users - What are the exact parameter variables for validity checker program for UPDDTA command? I gave them as FILE *CHR 10, FILELIB *CHR 10, MBR *CHR 10. It says ?Parameter does not match? - How do I find parameter declaration in validity checker program for ANY OS/400 command? - I tried to handle it using QIBM_QCA_RTV_COMMAND and QIBM_QCA_CHG_COMMAND insted validity checker program. Every thing is fine but I don?t know how to cancel the command processing program as it ignore any escape or diagnosis messages. But in validity checker program you can use escape and diognastic messages to cancel the command processing program

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello,

You can do a DSPCMD on the Library/Command and see the program for validity checking. If you need to change it, you can do the CHGCMD on the Command. Some of mine I have set as *NONE.

TPinky

====================================================

Generally, you don’t assign validity checker programs to commands that you didn’t create. The parameters are not documented — some command parameters are hidden. There is no way to predict if the parameters will be the same after applying PTFs or release upgrades.

If you don’t want a user to have access to a command, don’t give authority to run the command.

Tom

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • mcl
    In your question you state "My problem is restrict UPDDTA command for specific users". Are you trying to prevent them from using the command (which you can do using authorization to the command) or are you trying to restrict what the users can actually do with the command. For an UPDDTA, that would imply restricting the users from updating certain files, fields or maybe specific data content. You can restrict authority on files which would prevent the specific users from changing those files - and it is probably not a bad idea to do that anyway. If you are restricting how the command is used - you are probably better off writing an update program that provides specific editing capability. UPDDTA is handy, but it is far too easy to enter invalid data with it. On our system, no users (usrcls = *USER) have access to it. Regards Mike
    2,740 pointsBadges:
    report
  • Splat
    You'd probably be better off securing the command with an authorisation list. If you insist on changing the command, I'd recommend that you create a library for changed system objects & add it as the first entry of the system library list. Duplicate the command into this library, then change it - it makes it easy to return to the status quo ante & greatly reduces the chance of messing up a needed portion of the operating system.
    7,055 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following