The "model output file" [AKA "model outfile"] QAEZDISK ships in
QSYS in all releases that I can recall. Search the command name in
the following link; similar links all the way back to v4r5 are
available:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rbam6/rbam6clfiles.htm
As a model file, the processing for the command RTVDSKINF would
issue a CRTDUPOBJ QAEZDISK *NLVLIBL *FILE QUSRSYS *SAME DATA(*NO) to
create the copy of that file in QUSRSYS when it does not exist.
When that model outfile does not exist, the RTVDSKINF will fail.
The model output files are restored as part of the OS/400
language install. The system could be reinstalled to get the file
back, or any copy of the database *FILE object restored from a save
taken at another system on the same release level [unlikely the file
was changed by a PTF, so probably not specific to any PTF level on
any one release] and installed primary language would be acceptable
as well.
I am not sure why a copy in QUSRSYS is owned by QLPINSTALL, but
presume that for some reason the QUSRSYS install either at some old
release created the object [perhaps by the CRTDUPOBJ]. Of possibly
more interest for that situation could be the "created by", "create
date\time" and "release level" of that *FILE in QUSRSYS owned by
QLPINSTALL.
Regards, Chuck
DeLong, Eric wrote:
Should be in QUSRSYS. Mine (v5r4) shows owner QLPINSTALL, so it
looks like you either need to find it on a backup tape, or you'll
need to reinstall whatever feature delivers this tool...
Gary Kuznitz wrote:
I tried running the cmd RTVDSKINF in batch.
It gave me an error saying:
File QAEZDISK in library QSYS not found.
I did a search on the entire system for that file signed on as
QSECOFR.
It didn't find the file anyplace.
Does anyone know haw I can get that file back?
I'm running v4r4.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.