From: Charley Shanks To: All
I've been working with job descriptions, and I'm confused about the purpose of a couple of parameters: RTGDTA and RQSDTA or CMD. Why (or how) would these parameters ever be used?
From: Pete Hall To: Charley Shanks
The routing data (RTGDTA) is data that's compared with the subsystem's routing entries when a job is initiated, to determine what the routing program (a program that is run prior to any other programs a job calls) will be. It's usually QCMDx, but it doesn't necessarily have to be. You can get a feel for it if you display one of your subsystem descriptions and look at the routing entries.
The RQSDTA and CMD parameters are where you specify your command to execute. On the S/38 there was only RQSDTA. RQSDTA is still available for the same purpose, and has one advantage: it is a text string. You can use it the same way you would use QCMDEXC if you wanted to execute a text string in line, except you're submitting it. It's extremely useful if you need to submit a command with optional parameters, and you don't know which ones are used until execution time. You just construct your command by concatenating all the pieces into a variable, and then specify RQSDTA(&CMDTXT). Works great. If you specify your own routing program, I think you can also use this parameter to pass data to it, because the value is placed in the job log and can therefore be retrieved from the job's *EXT message queue.
From: Charley Shanks To: Pete Hall
Thanks. I still don't understand why you would ever want to change the routing entry. Smoke and mirrors.
From: James Coolbaugh To: Charley Shanks
Routing entries can be useful for setting certain jobs to different priorities within the same subsystem. They can also be used for validation of requests prior to execution of the request. I know of one such implementation; if a specific routing entry was encountered, a program was called that would interrogate the request. If the program was a compile, the routing entry would open the source member to retrieve any special compile options and tack them onto the request--all before the command was ever executed.
Normally, however, you don't have to worry about the routing entries. However, under certain conditions, there are valid reasons for changing a routing entry.
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