×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I got an off list response from someone who needed a little coffee.
Just for clarification...
The original SQL statement was this:
select QCMDEXC('SBMJOB JOB(' CONCAT MBFILE CONCAT ') CMD(RGZPFM FILE('
CONCAT MBLIB CONCAT '/' CONCAT MBFILE CONCAT ') MBR(' CONCAT MBNAME CONCAT
')'),
mbfile, mblib, mbndtr as DeletedCount, mbmxrl as MaxRcdLen,
mbndtr*mbmxrl as DeletedSpace, mbaccp
from qtemp/mbrinfo
where mbfila='*PHY' AND MBNDTR>0 AND MBFILE NLIKE 'QADB%'
order by mbndtr*mbmxrl desc
The resultant QCMDEXC is only this:
SBMJOB JOB(' CONCAT MBFILE CONCAT ') CMD(RGZPFM FILE(' CONCAT MBLIB CONCAT
'/' CONCAT MBFILE CONCAT ') MBR(' CONCAT MBNAME CONCAT ')')
or
SBMJOB JOB(MYFILE) CMD(RGZPFM FILE(MYLIB/MYFILE) MBR(MYMBR)
So, no, the submitted job doesn't care about the file QTEMP/MBRINFO
Think of it much like this simple CL program (without the appropriate
MONMSG or newer coding structures):
READ:
DCLF QTEMP/MBRINFO
RCVF
SBMJOB JOB(&MBFILE) CMD(RGZPFM FILE(&MBLIB/&MBFILE) MBR(&MBNAME)
GOTO READ
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
