Re: Restore QSYS2/SYSTABLES -- MIDRANGE-L

I am running V4R3.  If I do a CREATE COLLECTION sql statement it will build 
that 
view into the new library created by the CREATE COLLECTION statement.  Then I 
do a 
DSPFD newlib/SYSTABLES I will see the following right after the number of 
members.  
Notice the library name, PVC4XX, in the SQL statement.
SQL view create statement . . . . . . . . . :                         
  CREATE VIEW            SYSTABLES (TABLE_NAME FOR "NAME", TABLE_OWNER
   FOR "CREATOR", TABLE_TYPE FOR "TYPE", COLUMN_COUNT FOR "COLCOUNT", 
  ROW_LENGTH FOR "RECLENGTH", TABLE_TEXT FOR "LABEL", LONG_COMMENT FOR
   "REMARKS", TABLE_SCHEMA FOR "DBNAME", LAST_ALTERED_TIMESTAMP FOR "A
  LTEREDTS", SYSTEM_TABLE_NAME FOR "SYS_TNAME", SYSTEM_TABLE_SCHEMA FO
  R "SYS_DNAME") AS SELECT DBXLFI, VARCHAR(STRIP(DBXOWN,TRAILING),128)
  , SUBSTR(DBXATR,1,1), INTEGER(DBXNFL), INTEGER(DBXRDL), DBXTXT, DBXR
  EM,                                         VARCHAR(STRIP(STRIP(DBXL
  IB,TRAILING),BOTH,'"'),128), DBXATS, DBXFIL, DBXLIB FROM QSYS.QADBXR
  EF WHERE DBXREL = 'Y' AND DBXATR <> 'IX' AND DBXLIB = 'PVC4XX    '  
Record format selector program  . . . . . . : FMTSLR     *NONE        
Records to force a write  . . . . . . . . . : FRCRATIO       1        
Maximum file wait time  . . . . . . . . . . : WAITFILE   *IMMED       
Maximum record wait time  . . . . . . . . . : WAITRCD       60        
With check option . . . . . . . . . . . . . :            NONE         
Allow read operation  . . . . . . . . . . . :            Yes          
Allow write operation . . . . . . . . . . . :            No           
   Allow update operation  . . . . . . . . . . : ALWUPD     *NO    
   Allow delete operation  . . . . . . . . . . : ALWDLT     *NO    
   Record format level check . . . . . . . . . : LVLCHK     *YES   
   Access path . . . . . . . . . . . . . . . . :            Arrival
   Maximum record length . . . . . . . . . . . :             2497  
 Access Path Description                                           
   Access path . . . . . . . . . . . . . . . . :            Arrival
     Files accessed by logical file              PFILE             
        File               Library              LF Format          
        QADBXREF           QSYS                 SYSTABLES          
   Sort Sequence . . . . . . . . . . . . . . . : SRTSEQ     *HEX   
   Language identifier . . . . . . . . . . . . : LANGID     ENU    




IVANM@MULTIPOLAR.CO.ID on 11/10/98 02:00:52 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        Restore QSYS2/SYSTABLES

Hi All,
My customer could not create a new SQL from their PC to AS/400.
Apparently their lost the SYSTABLES  logical file on their production
machine (V3R7). 
These file reference to PF - QADBXREF.
Since SYSTABLES is an LF, can I just restore the SYSTABLES file from
"development machine" (V3R2) to the prod with option force conversion *YES.
and will this solve the problem ??
I'm not familiar with SQL. and Hope some advices .
Thanks.

regards,
Ivan.
 
 
+---
| 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
+---