Re: IBM recomendation-Long Obj Names & sub directories

Hello Steven,

>You wrote:

>1. Maximum length of object names from 10 bytes to 70 bytes
> Example CustomerMaster

You can already use 128-character names for database files **IF** you use SQL 
to 
create the files.  They can still be processed using native I/O.  However, this 
is 
implemented via a look-up table in the database cross-reference files.  The 
actual 
object name is still 10-characters.

You are extremely unlikely to get this passed for all objects.  The machine (as 
in MI) 
is architected for 30-character names.  I don't see that changing soon.  The 
CPF view 
of the machine is architected for 10-character names and while that could be 
increased 
to the 30-character machine limit there is a lot of work involved (commands, 
API's, 
panels, internal structures, etc.) and those resources could be better spent 
elsewhere.  Could you live with no new releases, no new products, no new 
function for 
the next two years?  It would take at least that long to do a complete change.

Externalising the 30-character name has been requested frequently over the life 
of the 
S/38 and AS/400 but has never been seen as important enough to get done.  Given 
Rochester's efforts to put Unix on the AS/400 I think you'll get your wish, 
just not 
in the manner you expected.

>2. Allow slashes in the library name
> Example JBA/AP/DATA

Really bad idea.  Apart from the difficulty of then parsing a path name, you 
end up 
with the horrible situation of the external name not reflecting the internal 
name 
because you must convert a slash in a name to something else ala the Micros~1 
kludge. 
Even HPFS and NTFS don't handle this nicely.  HPFS converts 'funny' characters 
such as 
slashes to an exlamation point, NTFS probably does something similar.  That 
means the 
command line names are different from the original GUI name.  I know that is 
true on 
OS/2.  Since NT is so similar I'd guess it suffers from the same problem.  I 
don't 
think Unix allows you to use the directory separator in a name.

The major issue then is that different client tools will show different names 
depending on whether they understand the new naming convention.  Like doing a 
DIR from 
DOS or OS/2 or Mac on a FAT32 partition.

It seems (from 3 below) that you really want a grouping function.  You can do 
that 
with the full-stop (or period in American parlance),  e.g., JBA.AP.DTA

>3. Allow generic libraries in the library list
> Example JBA/AP* JBA/GL*

Really bad idea.  Someone creates a new library with a partial match on a 
generic name 
and the library list for all jobs changes.  Ooops!  How would you organise the 
generic 
search path?  Simply alphabetically?  In order of creation?  Or like SBSD 
routing 
entries?  The real issue here is poor application design as evidenced by your 
choice 
of example. 25 libraries ought to be enough for anyone!  (Hmm, that sounds like 
"640K 
ought to be enough for anyone" -- B.G. or "10MB Winchester? No one will fill 
all that 
space" -- unknown)


>This would allow AS400 Internet applications to compete with NT & Unix.

I don't see how that would help.  Any names you can use on NT and Unix can be 
used in 
the IFS.  Store your html, JSP, java, and perl scripts in the IFS and you'ld 
never 
know what platform you were on.  If you must use HLL CGI (Brad and e-RPG 
notwithstanding) then use the HTTP MAP and PASS directives to use any external 
name 
you like.


Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| 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
+---