From: Michael Moschitta To: All
Our data center runs a weekly process that's dependent on an outside tape, so it can't be scheduled. However, the operators at the data center forget that Operational Assistant runs the daily backup automatically at 4:30 a.m. Each week, they start their job and it runs a while. Then the backup starts and eventually locks a file that the program tries to access. Of course, the CL program then blows up.
I want to add an exit program to the Operational Assistant backup to see if the data center's CL program is running. If it is not running, the backup should start; otherwise, the exit program needs to delay the backup and recheck periodically. The Check Active Program (CHKACTPGM) QUSRTOOL works great to check itself, but not another program-unless I'm doing it all wrong. Does someone have a better idea?
From: John Wagner To: Michael Moschitta
You can find out if a specific job is running by building logic into the job to let you know that it's there.
If the problem is contention for the tape drive, you could put something like the code in 3 in the front-end of all your jobs which might need to use the tape drive in question.
If the problem is contention for the tape drive, you could put something like the code in Figure 3 in the front-end of all your jobs which might need to use the tape drive in question.
Once past this bit of code, you are assured that the job containing it has control of the data area and, as a result, the tape drive. Other jobs containing this code will go into a five-minute wait state before retrying.
From: Matt Fulton To: Michael Moschitta
I suggest you create a data area. In the CL, change the data area to a known value, as shown below:
CHGDTAARA DTAARA(XXX) VALUE('ACTIVE')
As the last step in the CL, change the data area back to blanks:
CHGDTAARA DTAARA(XXX) VALUE('')
In the backup job, test the data area to determine if the CL program is running. This method has two advantages:
If the CL program terminates abnormally and you need to rerun it before the backup starts, the data area will still be "set" and the backup won't start. You can manually clear the data area or rerun the CL program.
The same data area can be used for all jobs that need to lock out the backup.
TechTalk: Avoid Tape Drive Conflicts
Figure 3 CL Code to Avoid Tape Drive Conflicts
ALCTAPE: CHKOBJ OBJ(QGPL/TAPEINUSE) OBJTYPE(*DTAARA) + AUT(*OBJEXIST) MONMSG MSGID(CPF9801) EXEC(DO) CRTDTAARA DTAARA(QGPL/TAPEINUSE) TYPE(*LGL) ENDDO ALCOBJ OBJ((QGPL/TAPEINUSE *DTAARA *EXCL)) WAIT(0) MONMSG MSGID(CPF1002) EXEC(DO) DLYJOB DLY(10) GOTO CMDLBL(ALCTAPE) ENDDO
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