While calling a command via a CL program exposes my command line.

1160 pts.
Tags:
AS/400
AS/400 commands
CL Commands
CL Program
CL programming
IBM iSeries
While calling a command via a CL program exposes my command line. Is it possible to hide the command line while executing the command via cl. I need to do this as iam executing the cl with adopted authority.

Software/Hardware used:
cl program, i570

Answer Wiki

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

The only way your command line should be appearing is if in your CL you call QCMD.
I am presuming you have a CL that does that and that program is setup with QSECOFR authority so you can do things without signing on as QSECOFR.
If that is the case, why do you need to hide the command line?
If I am misunderstanding you, please give us more information.
There are other things you can do, but before we give you other options, it would be better if you gave us the business case for what you are trying to accomplish and we can give you a specific answer,

Discuss This Question: 9  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
  • JohnsonMumbai
    Basic aim of the CL was to allow the user to run selected commands without exposing the command line, hence the program runs with adopted authority , but since the command line is exposed the purpose of using adopted authority is defeated.
    1,160 pointsBadges:
    report
  • CharlieBrowne
    Can you create a menu with each command that you want the user to run as a different menu option. They get the adopted authority when the enter the menu and lose it when they exit. There would be no command line on the menu. Would that work?
    41,380 pointsBadges:
    report
  • TomLiotta
    If the command is WRKSPLF or any other that supports a command line, then there is no way to suppress it. It's better to have the system set up so that it doesn't matter if users run commands. However, that's not an easy state to reach with older applications or with any applications that weren't created with appropriate security. If your users have been granted authority to run commands that can do damage, then the only defense is to avoid displaying a command line and to block access through network interfaces. Tom
    125,585 pointsBadges:
    report
  • HMSSL2K
    I like using menus with only options to run.
    3,175 pointsBadges:
    report
  • Batman47
    Yes, creating menus and having LMTCPB(*YES) set in the user profiles will allow you to run CL programs as menu options while hiding the command line.
    1,050 pointsBadges:
    report
  • JohnsonMumbai
    iam using the below two commands WRKOBJPDM LIB(QSYS) OBJ(QHST*) and WRKOBJ OBJ(&SCHAR) OBJTYPE(*DEVD)
    1,160 pointsBadges:
    report
  • JohnsonMumbai
    The above command is used by the operations team to 1. move objects from QHST library to another library. 2. To change the description of the devices of printers/ displays. This is used by the operations team and they do not have access to these files and hence these cl programs are run using adopted authority of user having *allobj access, the exposed command line gives the operations team *Allobj access while runing the mentioned commands.
    1,160 pointsBadges:
    report
  • JohnsonMumbai
    how do you avoid displaying a command line?
    1,160 pointsBadges:
    report
  • TomLiotta
    ...these cl programs are run using adopted authority of user having *allobj access... The authorities of the *OWNER will be used when the authority of the user is insufficient. Given your description, you're not as concerned with 'authority' as you are with 'capability'. This is used by the operations team... Set them as LMTCPB(*YES). That is, limit their 'capability' to use a command line to run commands. See if that helps. Command lines may still appear, but it won't make much difference if there are no commands that can be executed through those command lines. The real answer is not to use commands that provide features that you don't want used. That requires creating your own functions to use in place of WRKOBJPDM, WRKOBJ and others; but it gives you full and direct control over what any user might do. Tom
    125,585 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