× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,


I don't want to do this for my own commands, but for any command on the system.

A few examples;

- When a user performs "CALL PGM(X)" I want to block the command
- When a user performs "CALL PGM(Y)" I want to do a SBMJOB of it
- When a user performs "CALL PGM(Z)" I want to run it with adopted authority

While I can do the first with OS/400 object security, and the last by changing it to *OWNER... it is so dynamic that I can't use this approach. In this example it is the CALL command but it can be any of the 1000s of commands on the system.

Currently I solved this by programming a "fake command line" but whenever a user does for example WRKSPLF he gets a new command line that I no longer control (can avoid this with limit capabilities but that's not a nice solution neither).

?

Kind regards,

Paul


________________________________
From: Default <paultherrien@xxxxxxxxxxxxxxxxxx>
Sent: Monday, August 29, 2016 14:32
To: Midrange Systems Technical Discussion
Cc: Paul Nicolay
Subject: Re: Replace command processor


One option: create your own command to execute the IBM command and then you have 2 places where you can control how your command operates:

CRTCMD CMD(YOURCMD) PGM(YOURPGM) VLDCKR(YOURCHKR)

---

Paul





On 2016-08-29 07:29, Paul Nicolay wrote:

?Hi,


I wonder if it is possible to replace the OS/400 command processor ?

I would like to be able to control the command (ie. additional verifications and/or change) before it is executed.

Kind regards,
Paul


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.