I need to be careful when creating them to make sure that there is not another command of the same name 'higher' in the library list. I always create them in my own library, that way they are only mine. I only use the proxy commands as shortcuts on the IBM i command line. If I choose to delete my proxy command I would just use the Delete Command command, DLTCMD. If I need to change my proxy command I use the Change Proxy Command command, CHGPRXCMD. Now whenever I need to do WRKSPLF I can just type SP and the same command is executed. My new proxy command can be identified as one by the object attribute of PRX, which non-proxy commands do not have. MYLIB Opt Object Type Attribute Text ANOTHER *CMD Another command When I press the Enter key the proxy command is created. There are additional parameters, you can see by pressing F10, but I have never found a use for them. There is no reason why I could not use something like: 'Simon's WRKSPLF proxy' if I so choose. This gives my proxy command the same description as the target command.

I leave the library as *LIBL as the WRKSPLF command is in the library QSYS, which should be in everyone's library list. In the command parameters I have entered the name I wish to call my proxy command, SP, and the library it will reside in, MYLIB.Īs this is my shortcut for WRKSPLF then the target command is WRKSPLF. In this example I am going to create a proxy command, SP, for the Work with Spooled Files command, WRKSPLF. You can even make proxies of proxy commands, although I cannot think of a reason why I would ever think to do so.

These allow me to create shortcut commands of the regular IBM i commands without any programming. I don't think many people know of proxy commands. In one example the command SP did the same as WRKSPLF. After my post about how to create your own commands I received messages from readers giving me examples of how they have created their own shortcut commands, to do the same as the standard IBM i command but shorter.

As400 command line commands