Did you know you could use KILL rather than ENDJOB?
Over the years, many users have assigned their own names to various IBM-provided commands. Historically, they may have duplicated the IBM command to another library, changing the name, or they may have written their own command and command processing program (CPP), which then used the IBM-provided command. These approaches have drawbacks--a major one being that release changes to the IBM commands (new parameters, new parameter values, etc.) would often cause those users to have to also change their instance of the command. With V5R4, IBM provides a much easier way to use your own names for existing commands.
The enabler for this new support is the Create Proxy Command (CRTPRXCMD) command, which is documented here. This command allows us to provide an alias, or alternative name, to another command. For instance, to have the system support KILL as being synonymous with the ENDJOB command, you would use the following CRTPRXCMD command:
CRTPRXCMD CMD(VINING/KILL) TGTCMD(ENDJOB)
This command creates a new user-defined proxy command named KILL in library VINING. When you run or prompt the KILL command, you will actually be running or prompting the ENDJOB command.
When you create a proxy command, you do not specify any command definition source. The proxy command does not contain any parameter definition information, prompt control information, validity checking information, or environment information. When the proxy command is used, all of this information is inherited from the target command (TGTCMD) specified with the CRTPRXCMD command. This inheritance by the proxy command is great in that you are no longer tied to the IBM definition of the target command. This means that release-to-release changes will not impact you in the way duplicating the IBM command might have in the past.
This inheritance has a drawback, however. It also means that you cannot selectively change command defaults with the Change Command Default (CHGCMDDFT) command. Any change to the KILL proxy using CHGCMDDFT actually changes the underlying target command ENDJOB. So you cannot, for instance, use the CHGCMDDFT command to have the original command ENDJOB default to OPTION(*CNTRLD) while the KILL proxy defaults to OPTION(*IMMED). Notice though that I have qualified this restriction in terms of using CHGCMDDFT. There is a way to have KILL use OPTION(*IMMED) while ENDJOB uses OPTION(*CNTRLD), and we'll look at this shortly.
As you can see, creating a Proxy command is quite simple. The first proxy command I created was for the SIGNOFF command. Perhaps it's only me, but when I'm in a hurry, I frequently type SINGOFF rather than SIGNOFF. This typo simply delays me when I'm already in a rush. So I was more than happy to use the following command and avoid future delays due to this error.
CRTPRXCMD CMD(SINGOFF) TGTCMD(SIGNOFF) TEXT('Bruce''s SIGNOFF')
You, if moving to the i from another environment, may likewise want to utilize proxy commands. If you are familiar with the S/36 environment, creating a proxy named OFF for SIGNOFF might be useful. In a similar vein, the proxy LOGOFF may be appropriate for some users.
In addition to the CRTPRXCMD command, there is also the Change Proxy Command (CHGPRXCMD) command to change a proxy command. When changing the proxy command, you can only change the target command and the text description of the proxy. Other characteristics of the proxy command are maintained using traditional commands. For instance, to delete a proxy command, you use the existing Delete Command (DLTCMD) command. To change the public authority of the proxy command, you might use the existing Grant Object Authority (GRTOBJAUT) command as in this example:
GRTOBJAUT OBJ(VINING/SINGOFF) OBJTYPE(*CMD) USER(*PUBLIC) AUT(*ALL)
Earlier, I mentioned that you could have the KILL proxy command use OPTION(*IMMED) of the target ENDJOB command while the ENDJOB command itself continued to use OPTION(*CNTRLD) by default. You can do this by using the Command Analyzer Change exit point QIBM_QCA_CHG_COMMAND, which is documented here. The Command Analyzer Change exit point can call a user-written exit program when a particular command is run. The command to run, when using proxies, is the target command--ENDJOB in our case. When the exit program is called, the user program generally can replace the command that was originally requested or, as is our case, specify additional parameters, such as OPTION of ENDJOB. The exit program is passed several fields of information. One key piece of information that we will use is the proxy chain used to finally get to the ENDJOB command being run.
In the next article, we will look at a sample program that is called whenever the ENDJOB command is processed. This sample program will determine if the ENDJOB command was reached by way of the KILL proxy command. If KILL was used, the exit program will then add OPTION(*IMMED) to the command string to be run.
More CL Questions?
Wondering how to accomplish a function in CL? Send your CL-related questions to me at
Bruce Vining is president and co-founder of Bruce Vining Services, LLC, a firm providing contract programming and consulting services to the System i community. He began his career in 1979 as an IBM Systems Engineer in St. Louis, Missouri, and then transferred to Rochester, Minnesota, in 1985, where he continues to reside. From 1992 until leaving IBM in 2007, Bruce was a member of the System Design Control Group responsible for OS/400 and i5/OS areas such as System APIs, Globalization, and Software Serviceability. He is also the designer of Control Language for Files (CLF).A frequent speaker and writer, Bruce can be reached at
MC Press books written by Bruce Vining available now on the MC Press Bookstore.
 |
||
 |
|
IBM System i APIs at Work Leverage the power of APIs with this definitive resource. List Price $89.95 Now On Sale
|
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online