|
Bill, The IBM Redbook "Geac System 21 - Implementation for AS/400" is an excellent resource http:/www.redbooks.ibm.com/abstracts/sg245967.html and has great examples of naming conventions. See Chapter 11 (Customization) and page 390 for specifics. One other thing to consider is if you create logicals over System 21 physicals you might want to have custom libraries with a name that is lower in the iSeries sorting order. Our custom libraries all start with the first letter of 'Z'. The reason for this is in the event of system restore resulting from a disaster, a disaster test, hard drive failure, etc. when you restore your libraries it is generally done via a RSTLIB *NONSYS or some equivalent method. These methods restore the libraries alphabetically starting with 'A'. The restore can not restore logical files if the physicals do not already exist on the system. In our case all of the System 21 and other libraries will be restored before any of our custom 'Z' libraries. I hope this makes sense as it is a very important concept. Worst case is that if you did not use this library naming convention you would have to manually recreate or restore all of your logicals after everything else was restored in a disaster. However, you usually have plenty of other things to keep you busy in a disaster and this would delay recovery. Steve Prill Senior I.S. Project Manager Rexair LLC -----Original Message----- From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of JBA Consultant Sent: Wednesday, September 14, 2005 7:08 AM To: 'System 21 Users' Subject: RE: [SYSTEM21] Creating PF's or LF's Bill, It's common practice to suffix the file or program with a U. eg. OEP72U Also to put the object into a non GEAC library. Eg. OSLRICP3 for programs or OSLRICf3 for files. Associate a program with a task number in the 99xxxx range. I hope that this helps. Marcus. -----Original Message----- From: system21-bounces+jba.consultant=virgin.net@xxxxxxxxxxxx [mailto:system21-bounces+jba.consultant=virgin.net@xxxxxxxxxxxx] On Behalf Of Bill.Geissinger@xxxxxxxxxxxxxxxxx Sent: 13 September 2005 19:38 To: system21@xxxxxxxxxxxx Subject: [SYSTEM21] Creating PF's or LF's When creating new PF's or LF's does GEAC recommend customer's using a certain range when creating these files so you don't duplicate a GEAC file name that may be used in the future? Also, is their a standard when creating program names also? Bill Geissinger _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. This email and any attachment are confidential and may be legally privileged. If you are not the intended recipients, please notify the author by replying to this email message, and then delete all copies of the email on the system. If you are not the intended recipient, you must not disclose, distribute, copy, print or use this email in any manner. Email messages and attachments may contain viruses. Although we take precautions to check for viruses, we make no assurances about the absence of viruses. We accept no liability and suggest that you carry out your own virus checks.
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.