CHKTAP will not handle the BRMS side of things, such as if a valid BRMS scratch tape is in the drive. I tried monitoring message on BRM0000 and CPA0000 but it did not catch CPA message CPA4086. The tape drive, which is a 3580, tried to load the next tape when it saw that the tape in the drive was an Active BRMS tape and not a scratch tape. There was not any other tapes in the drive, then causing the CPA message. Any other ideas? NF Subject: Re: BRMS in CL From: "Jim Franz" <franz400@xxxxxxxxxxxx> Date: Wed, 31 Mar 2004 11:54:47 -0500 List-archive: <http://archive.midrange.com/midrange-l> List-help: <mailto:midrange-l-request@xxxxxxxxxxxx?subject=help> List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com> List-post: <mailto:midrange-l@xxxxxxxxxxxx> List-subscribe: < http://lists.midrange.com/mailman/listinfo/midrange-l>, < mailto:midrange-l-request@xxxxxxxxxxxx?subject=subscribe> List-unsubscribe: < http://lists.midrange.com/mailman/listinfo/midrange-l>, < mailto:midrange-l-request@xxxxxxxxxxxx?subject=unsubscribe> use the CHKTAP to verify the tape is ready. see the help text for all the monmsg id's jim ----- Original Message ----- From: "Nick Franco" <franco.nick@xxxxxxxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, March 31, 2004 8:19 AM Subject: BRMS in CL > I have a BRMS question for those familiar. We currently have a CL that does > our nightly processing and backups. We are going to replace the SAVLIB with > STRBKUBRM. The CL already runs in batch and the STRBKUBRM cmd will be > entered as SBMJOB(*no) so it will continue in the same CL. The problem is > this: We need to monitor messages for the STRBKUBRM so that, if there is no > tape loaded or a scratch tape is not loaded, the CL will continue and > complete the rest of the steps it needs to complete. We do not want to > replace the CL with a BRMS control group that has multiple *EXITs because > it can be run with different parameters. What MONMSGs are needed or how > else can we make this work? Thanks. > > NF > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.