RE: syspackage

The libraries that were restored did have SQL instructions so...the AS400
created the SYSPACKAGE automatically. Just because it was a different
SYSPACKAGE name doesn't seem to manner(I hope).
What threw me off on restoring this C program was the program names were 12
characters long. As you probably already know, the AS/400 can only have
table names (physical files) with 10 character names, so what it does is
take the first five (5) characters of the SQL table name and then append a
five (5) digit number.  The numbers start with 00001 (for a given five
character name) and increments up each time a new object is created, and
these numbers can be reused.
if you save the table (physical file) when it has a short name of 00010,
then start using a new short name of 00023, then want to put 00010 back on
the system, you have to check for two things:

1) Is 00010 now being used by another long name?  Since these numbers can
be reused, another newly created table or view may have grabbed that short
name?
2) Does the long name currently have a short name associated with it?
Again, you can't have two short names in the same library for the same long
name. 
One of these two things caused the restore problem and then this SYSPACKAGE
rename was a new one for me.
Thanks for your help!
Art 
-----Original Message-----
From: Dave Miller [mailto:dlmiller@jquint.com]
Sent: Monday, June 26, 2000 12:13 PM
To: MIDRANGE-L@midrange.com
Subject: RE: syspackage


on the As/400, a package is what is created when a program with imbedded SQL
calls is compiled.
All programs, RPG, C, Cobol, Jave etc.  create a package to store the SQL
security, execution instructions, etc in.  It is physically a separate
object from the program object.
Some software/hardware platforms require you to create a program, then the
package that contains the SQL calls.  The AS/400 creates the packages
automatically whenever a program with SQL instructions in it is compiled.
Optionally there is an AS/400 command (CRTSQLPKG) that will look at a
compiled program object and generate a package.

> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Rob Berendt
> Sent: Monday, June 26, 2000 8:39 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: syspackage
>
>
> *SQLPKG is one of many objects created in a library when
> the library is created in SQL using the CREATE PACKAGE command
> versus using the OS/400 command CRTLIB.  As to what it is, or
> what it does, I've not a clue.
>
>
>
>
>
> Art_Baker@baan.com on 06/21/2000 12:59:41 PM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:
> Fax to:
> Subject:      syspackage
>
> Hi,
>       Can someone explain how SYSPACKAGE is used on the AS400. The
> situation was someone called in (I work on a help desk) and their
> production
> company was corrupted, called company 120. They renamed company 120, had a
> journal problem. Ended journal. Deleted, or renamed company 120. Restored
> the company from tape and received a SYSPACKAGE error. It was a
> priority 10
> error which mentioned the SYSPACKAGE was renamed to SYSPACK001or maybe
> SYSPACKAGE001. They didn't like this so they deleted and restored again
> omitting the SYSPACKAGE so they would not see this error. This is
> when I was
> called because they could not log into their ERP system, logging on to the
> AS400 was OK. There was a error CPF4328-file is not journaled.
> Tried turning
> journaling off and on, no change. Ended and restarted their ERP system, no
> change. Ended up restoring their ERP library and now they can access their
> production company.
>       I'm guessing their journals were 'out of sync' with the company and
> would not journal the company files?. Where does SYSPACKAGE fit in
> performing restores? Is there something else I could have done besides
> restoring their ERP library?
> TIA
> Art
> +---
> | 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
+---