RE: IFS name in QAEZDISK from RTVDSKINF/PRTDSKINF -- MIDRANGE-L

Um, wait.  QAEZDISK has the folder path at the end of the file.  Regardless,
IBM's wrong and I'm right.  :)

You have to admit that it looks screwy when you pull up the QAEZDISK file
and has entries that say:

"there an object on your system.  it's a stream file.  it doesn't have a
library.  it's using 42318 bytes of storage.  it was created on 4/12/2000,
by user QSYSOPR.  but I can't tell you what it's called or where it is.
Would it help if I told you what ASP it's in?"


James Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: Jim Damato 
Sent: Wednesday, May 16, 2001 2:09 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: IFS name in QAEZDISK from RTVDSKINF/PRTDSKINF


How long are the individual directory names?  The record structure of the
QAEZDISK file used by RTVDSKINF does not hold the entire path for shared
folders either.  Each file or folder is listed with its parent folder name.
You can construct the path by tracking the folders and parent folders.

The IFS itself is a bit unwieldy when compared to ten-character object names
in ten-character library names.  Nonetheless I would like to see the
Integrated File System actually become integrated.  Since the introduction
of the IFS I've thought that it was a great opportunity to open the AS/400
to Unix and Microsoft users.  It's taking a long time to get there, IMHO.


James Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: Alexei Pytel [mailto:pytel@us.ibm.com]
Sent: Wednesday, May 16, 2001 1:02 PM
To: MIDRANGE-L@midrange.com
Subject: RE: IFS name in QAEZDISK from RTVDSKINF/PRTDSKINF



You probably want to see entire IFS path name.
IFS path names are architectiured to be up to 16MB long - a bit unwieldy.

    Alexei Pytel




 

                    Jim Damato

                    <jdamato@dollargene       To:
"'MIDRANGE-L@midrange.com'"                  
                    ral.com>                   <MIDRANGE-L@midrange.com>

                    Sent by:                  cc:

                    owner-midrange-l@mi       Subject:     RE: IFS name in
QAEZDISK from           
                    drange.com                 RTVDSKINF/PRTDSKINF

 

 

                    05/16/2001 11:19 AM

                    Please respond to

                    MIDRANGE-L

 

 




Years of dealing with vendor software solutions have reinforced that
creeping feeling of futility I get whenever I submit an "enhancement
request".  Submitting the request, however, was a good idea.  I don't know
how you resisted the urge to type "duhh!" somewhere on the form.


Select a requirement type: (Select one)

  ___ Long range or strategic (required to meet long-range needs)
  ___ Suggestion (you would like, but it is not critical)
  ___ Tactical (needed to solve a short-term problem)
  _X_ An embarrassingly obvious design oversight



-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Wednesday, May 16, 2001 9:23 AM
To: MIDRANGE-L@midrange.com
Subject: IFS name in QAEZDISK from RTVDSKINF/PRTDSKINF


This is their reply.

I guess you could use the request form for all sorts of requests.

Rob Berendt

==================
Remember the Cole!
----- Forwarded by Rob Berendt/DEKKO on 05/16/01 09:22 AM -----


                    "James

                    Vessey"              To:     rob@dekko.com

                    <v40915@us.ib        cc:

                    m.com>               Subject:     Please add the name
of
the IFS object to the file QAEZDISK
                                         created by

                    05/16/01

                    09:13 AM









We have received and entered your request for a design change. Your
Requirement Number is MR  051601174

Document Status - Acknowledged
Title - Please add the name of the IFS object to the file QAEZDISK created
by
RTVDSKINF/PRTDSKINF.

IBM has received this requirement and someone is evaluating it. An
additional response will be given before the end of this measurement cycle
(currently 90 days from the date submitted).
Thank you for your input to the AS400.

*******************************************************
 James Vessey
 Business Operations Desk
 AS400 Support Center
 (507)-286-6284, T/L 456-6284   E-Mail: v40915@us.ibm.com
 Dept LYCA: Building 664-3 G198: Rochester, MN




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---