Add DST Catalog Entry (ADDDSTCLGE)

The Add Distribution Catalog Entry (ADDDSTCLGE) command is used to add an entry to the distribution catalog. A data object can optionally be loaded into the distribution repository from an i5/OS library, folder, or from any of the integrated file systems.

The distribution catalog contains a list of objects that are eligible for distribution. Each catalog entry is identified by a network-wide unique name called a global name. Each catalog entry describes where the object to be distributed is located for retrieval or can be stored when received.

The catalog entry consists of the global name of the object, the name of the object's storage location (if the object exists), and attributes of the object. The data object associated with the global name can be stored as a standard i5/OS object in a library, folder, stream file, or distribution repository.

Notes:

1. When the object type *LICKEY is specified, it is assumed that the file that is to be cataloged is a license key file.
2. A specific format to catalog a license key file or a stream file for a global name is not required.
3. A specific global name format is required to catalog an installable object.

Parameters

Keyword	Description	Choices	Notes
GLBNAME	Global name	Element list	Required, Positional 1
	Element 1: Global name token 1	Character value, *NETID, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 2: Global name token 2	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 3: Global name token 3	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 4: Global name token 4	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 5: Global name token 5	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 6: Global name token 6	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 7: Global name token 7	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 8: Global name token 8	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 9: Global name token 9	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
	Element 10: Global name token 10	Character value, *NETID, *CPNAME, *DATE, *TIME, *MDDATE, *MDTIME, *SERVER, *TARGET
OBJTYPE	Object type	Character value	Required, Positional 2
OBJ	Object	Single values: *NONE Other values: Qualified object name	Optional, Positional 3
	Qualifier 1: Object	Name
	Qualifier 2: Library	Name, *LIBL, *CURLIB
MBR	Member	Name, *ALL, *FIRST	Optional, Positional 4
DATATYPE	Data type	*UNSPEC, *CL, *REXX	Optional, Positional 5
DLO	Document library object	Character value, *NONE	Optional, Positional 6
FLR	Folder	Character value, *NONE	Optional, Positional 7
STMF	Stream file	Path name, *NONE	Optional, Positional 8
STGLOC	Local storage location	*STD, *DSTRPS	Optional
TGTRLS	Target release	*CURRENT, *PRV, V5R4M0, V6R1M0, V7R1M0	Optional
DTACPR	Data compression	*NONE, *SNA	Optional
SNACPRCHR	Compression character	00-FF, *BLANK	Optional
AUTL	Authorization list	Name, QCQRPSAUTL	Optional
DTAACCKEY	Data access key	Character value, *NONE	Optional
TEXT	Catalog entry text	Character value, *OBJTEXT, *BLANK	Optional
VERSIONATR	Version attributes	Element list	Optional
	Element 1: Global name token 1	*UNSPEC
	Element 2: Global name token 2	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 3: Global name token 3	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 4: Global name token 4	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 5: Global name token 5	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 6: Global name token 6	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 7: Global name token 7	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 8: Global name token 8	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 9: Global name token 9	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
	Element 10: Global name token 10	*UNSPEC, *NETID, *CPNAME, *ORDCHAR, *ORDDATE, *ORDDEC, *ORDTIME, *STI, *SYSTYPE
MATCHATR	Match attributes	Element list	Optional
	Element 1: Global name token 1	*MATCH
	Element 2: Global name token 2	*NOMATCH, *MATCH
	Element 3: Global name token 3	*NOMATCH, *MATCH
	Element 4: Global name token 4	*NOMATCH, *MATCH
	Element 5: Global name token 5	*NOMATCH, *MATCH
	Element 6: Global name token 6	*NOMATCH, *MATCH
	Element 7: Global name token 7	*NOMATCH, *MATCH
	Element 8: Global name token 8	*NOMATCH, *MATCH
	Element 9: Global name token 9	*NOMATCH, *MATCH
	Element 10: Global name token 10	*NOMATCH, *MATCH

Top

Global name (GLBNAME)

Specifies the token values of the global name. The global name is the name by which the object is known in a system network architecture (SNA) network. The global name can be a maximum of 65-n characters in length, where n is the number of tokens. A maximum of 10 tokens can be specified and each token can be a maximum of 16 characters in length.

Valid tokens consist of uppercase letters A-Z and numbers 0-9. The special characters #, $, or @ are valid only when VERSIONATR(*CPNAME) is specified. In multilingual networks, language translation may make the value not valid when the special characters are used. Use of these characters is not recommended.

Notes:

1. The global name must contain at least one token with VERSIONATR(*STI) specified when adding a distribution catalog entry for a product.
2. If OBJTYPE(*PRODUCT) is specified, global names can have up to a maximum of 7 tokens before VERSIONATR(*STI) is specified, and a maximum of 2 tokens after VERSIONATR(*STI) is specified.
3. At least two tokens must be specified in the global name.
4. *SERVER, *TARGET, *MDDATE, and *MDTIME values are valid for token 1 or token 2.

This is a required parameter.

The possible token 1 values are:

*NETID

The first global name token value is a network ID generated by the command from the network attributes. VERSIONATR(*UNSPEC) or VERSIONATR(*NETID) must be specified.

*MDDATE

This token is stored within the change request activity with the value &DATE, and replaced when distributed by the date the object was last modified.

*MDTIME

This token is stored within the change request activity with the value &TIME, and replaced when distributed by the time the object was last modified.

*SERVER

This token is stored within the change request activity with the value &SERVER, and replaced by the short name of the change control server when the object is distributed.

*TARGET

This token is stored within the change request activity with the value &TARGET, and replaced by the short name of the target when the object is distributed.

global-name-token

Specify the first token of the global name. The first token is recommended to be the registered enterprise ID or network ID.

The possible subsequent token values are:

*NETID

Identifies the global name token n value as a network ID. This value is generated from the network attributes. VERSIONATR(*UNSPEC) or VERSIONATR(*NETID) must be specified for the corresponding token.

*CPNAME

Identifies the global name token value as a control point name. This value is generated from the network attributes. VERSIONATR(*UNSPEC) or VERSIONATR(*CPNAME) must be specified for the corresponding token.

*DATE

Identifies the global name token value as the current date. This value is generated from the system value with the format Y1992M04D10. VERSIONATR(*UNSPEC), VERSIONATR(*ORDDATE), or VERSIONATR(*ORDCHAR) must be specified for the corresponding token.

*TIME

Identifies the global name token value as the current time. This value is generated from the system value with the format H13M30S20. VERSIONATR(*UNSPEC), VERSIONATR(*ORDTIME), or VERSIONATR(*ORDCHAR) must be specified for the corresponding token.

*MDDATE

This token is stored within the change request activity with the value &DATE, and replaced when distributed by the date the object was last modified.

*MDTIME

This token is stored within the change request activity with the value &TIME, and replaced when distributed by the time the object was last modified.

*SERVER

This token is stored within the change request activity with the value &SERVER, and replaced by the short name of the change control server when the object is distributed.

*TARGET

This token is stored within the change request activity with the value &TARGET, and replaced by the short name of the target when the object is distributed.

global-name-token

Specify a token of the global name.

Object type (OBJTYPE)

Specifies the type of object used.

This is a required parameter.

*FILEDATA

A file member containing data is transferred without attributes. The MBR parameter is required when OBJTYPE(*FILEDATA) is specified and OBJ(*NONE) is not specified.

*PRODUCT

A save file containing a product packaged with the i5/OS product packaging support.

*LICKEY

A license key file generated through the Display License Key (DSPLICKEY) command. The MBR parameter is required when *LICKEY is specified and the OBJ parameter is not *NONE.

*STMF

A stream file containing a continuous stream of data.

*INSOBJ

An installable object containing a combination of objects to be installed and a list of those objects associated with the name of the target library, folder, or path where the objects must be created when the installable object is installed.

object-type

Specify the i5/OS object type to be used.

Object (OBJ)

Specifies the qualified name of the object to be used when adding the catalog entry.

The possible single value is:

*NONE

A data object is not loaded into the repository. OBJ(*NONE) is only valid when STGLOC(*DSTRPS) is specified.

The name of the object can be qualified by one of the following library values:

*LIBL

All libraries in the job's library list are searched until the first match is found.

*CURLIB

The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

library-name

Specify the name of the library to be searched.

The possible object name value is:

object-name

Specify the name of the local object.

Member (MBR)

Specifies the file member to be used when OBJTYPE(*FILEDATA), OBJTYPE(*FILE), or OBJTYPE(*LICKEY) is specified.

*ALL

When STGLOC(*DSTRPS) is specified, the entire file is loaded into the distribution repository and a catalog entry is added to the catalog for the repository object. When STGLOC(*STD) is specified, a catalog entry is added for the file. MBR(*ALL) is only valid when OBJTYPE(*FILE) is specified.

*FIRST

When STGLOC(*DSTRPS) is specified, the first file member is loaded into the distribution repository and a catalog entry is added to the catalog for the repository object. When STGLOC(*STD) is specified, a catalog entry is added for the first member.

member-name

Specify the name of the file member to be used.

Data type (DATATYPE)

Specifies the type of data contained in a member that is handled as data only, without attributes. This parameter is only valid when OBJTYPE(*FILEDATA) is specified.

*UNSPEC

The data type is not specified.

*CL

The data type is control language (CL).

*REXX

The data type is REXX.

Document library object (DLO)

Specifies the document library object name being cataloged. This parameter is required when OBJTYPE(*DOC) is specified.

*NONE

A document is not loaded into the distribution repository. DLO(*NONE) is only valid when STGLOC(*DSTRPS) is specified.

document-name

Specify the name of the document to be cataloged. Valid document names can be up to eight characters in length and optionally qualified with a period and a one to three character extension.

Folder (FLR)

Specifies the folder name in which the document specified on the DLO parameter is located. This parameter is required when OBJTYPE(*DOC) or OBJTYPE(*FLR) is specified.

*NONE

No folder or document is loaded into the repository. This parameter is only valid when STGLOC(*DSTRPS) is specified.

folder-name

Specifies the name of the folder in which the document is located or the folder name is being cataloged. The folder name can be a maximum of 63 characters in length.

Stream file (STMF)

Specifies the stream file to be cataloged. This parameter is required when OBJTYPE(*STMF) is specified.

*NONE

No stream file is loaded into the distribution repository. This parameter is only valid when STGLOC(*DSTRPS) is specified.

object-path-name

Specifies the path name of the stream file. This can be a path name of 1980 characters. Additional information about path names is in the Integrated File System Introduction book.

Local storage location (STGLOC)

Specifies the storage location of the data object to which the global name points.

*STD

The global name refers to the object specified on the OBJ name parameter.

*DSTRPS

The global name refers to an object in the distribution repository. If an object is specified on the OBJ parameter, it is loaded into the repository.

Target release (TGTRLS)

Specifies the release of the operating system on which you intend to use the object. This parameter is ignored when OBJTYPE(*FILEDATA), OBJTYPE(*PRODUCT), OBJTYPE(*LICKEY), OBJTYPE(*STMF), OR OBJTYPE(*INSOBJ) is specified, or the object is a save file.

*CURRENT

The object is used on the release of the operating system currently running on your system. If V7R1M0 is running on your system, *CURRENT means that you intend to use the object on a system with V7R1M0 installed. The object also can be used on a system with any later release of the operating system installed.

release-level

Specify the release level in the format VxRxMx. The object is used on a system with the specified release or with any later release of the operating system installed.

Valid values depend on the current version, release, and modification level, and they change with each new release.

Data compression (DTACPR)

Specifies the compression method used to load a member into the distribution repository.

*NONE

The object is not compressed.

*SNA

The object is compressed using SNA compression.

Compression character (SNACPRCHR)

Specifies the prime compression character used by the SNA compression algorithm when DTACPR(*SNA) is specified. Valid values range from hexadecimal '00'X through 'FF'X. This parameter is ignored when DTCPR(*NONE) is specified.

*BLANK

The prime compression character is a blank (hexadecimal value '40'X ).

character

Specify the hexadecimal value of the prime compression character to be used.

Authorization list (AUTL)

Specifies the name of the authorization list of the repository object. This parameter is required when STGLOC(*DSTRPS) is specified.

QCQRPSAUTL

The default authorization list is used.

authorization-list-name

Specify the name of the authorization list to be used.

Authorization list (DTAACCKEY)

Specifies the data access key (DAK) associated with the file. If this value is specified, the data access key name must exist in the access key table. This access key protects the catalog entry when used in the change control server/client environment.

*NONE

No access key is assigned to the catalog entry.

access-key

Specify the name of the data access key (DAK) associated with the file.

Catalog entry text (TEXT)

Specifies the text description of the catalog entry.

*OBJTEXT

The text description of the local object is used. This value is not valid when OBJ(*NONE) is specified.

Note: When cataloging a stream file and *OBJTEXT is used for the text parameter, the catalog entry description for the stream file being cataloged is generated with the text Catalog entry for a stream file.

*BLANK

No text is specified.

'description'

Specify no more than 50 characters of text, enclosed in apostrophes.

Version attributes (VERSIONATR)

Specifies the version attributes of the tokens in the global name. The attributes identify the kind of token.

The possible value for token 1 is:

*UNSPEC

The version attribute is not specified.

The possible values for tokens 2-10 are:

*UNSPEC

The version attribute is not specified.

*NETID

The corresponding token is a network ID.

*CPNAME

The corresponding token is control point name.

*SYSTYPE

The corresponding token is a system type.

*STI

The corresponding token is a subtree indicator.

The tokens with the following attributes may be used in partial matching:

*ORDCHAR

The corresponding token is an ordered character.

*ORDDATE

The corresponding token is an ordered date with the format Y1989M05D03.

*ORDDEC

The corresponding token is an ordered decimal.

*ORDTIME

The corresponding token is an ordered time with the format H13M30S20.

Match attributes (MATCHATR)

Specifies whether each token in the global name must match the corresponding token on the global name in the request when partial global name matching is done.

The possible value for token 1 is:

*MATCH

The requested token must match this token.

The possible values for tokens 2-10 are:

*NOMATCH

The requested token is not required to match this token. This match attribute should be specified for all tokens that have VERSIONATR(*ORDDATE, *ORDTIME, *ORDCHAR, or *ORDDEC) specified.

*MATCH

The requested token must match this token.

Examples

Example 1: Adding a Catalog Entry for a File

ADDDSTCLGE   GLBNAME(ENTID FINANCE PAYROLL DEDUCT)
             OBJTYPE(*FILE)  OBJ(*LIBL/PAYDED)  STGLOC(*STD)

This command adds a catalog entry for the payroll deductions file. All requests received referring to global name ENTID FINANCE PAYROLL DEDUCT are performed on the file PAYDED.

Example 2: Loading a File into the Repository for Filedata

ADDDSTCLGE   GLBNAME(ENTID INVENTORY *DATE)  OBJTYPE(*FILEDATA)
             OBJ(APPLZ/CURINV)  MBR(*FIRST)  STGLOC(*DSTRPS)
             DTACPR(*SNA)  AUTL(MYLIST)
             VERSIONATR(*UNSPEC *ORDCHAR *ORDDATE)
             MATCHATR(*MATCH *NOMATCH *NOMATCH)

This command loads the current inventory file APPLZ in library CURINV into the distribution repository in compressed form. The file in the distribution repository can be referred to by the global name ENTID INVENTORY Y1993M09D15. The file is secured by authorization list MYLIST.

Example 3: Loading a Document into the Repository for a Document

ADDDSTCLGE   GLBNAME(ENTID NYPS1 SALESRPT)  OBJTYPE(*DOC)
             DLO(STATUS)  FLR(NY/SALES.RPT/APRIL)
             STGLOC(*DSTRPS)

This command loads document STATUS in folder path NY/SALES.RPT/APRIL into the distribution repository.

Example 4: Adding a Distribution Catalog Entry into the Repository for a Product

ADDDSTCLGE   GLBNAME(I3IBM1 AS400 ACCOUNT V1R1M0 BASE ALL 2924
               REF 001 V5R2M0)  OBJTYPE(*PRODUCT)
             OBJ(ACCLIB/ACCPKG)  STGLOC(*DSTRPS)
             VERSIONATR(*UNSPEC *ORDCHAR *ORDCHAR *ORDCHAR
               *ORDCHAR *ORDCHAR *ORDCHAR *STI *ORDDEC *ORDCHAR)
             MATCHATR(*MATCH *NOMATCH *NOMATCH *NOMATCH *NOMATCH
               *NOMATCH *NOMATCH *NOMATCH *MATCH *NOMATCH
               *NOMATCH)  TEXT('Accounting Base Product V1R1M0')

This command adds an entry to the Distribution Catalog and points to a product stored in the distribution repository.

Example 5: Adding an Entry into the Distribution Catalog for a Product

ADDDSTCLGE   GLBNAME(I3IBM1 AS400 DISTSYS V1R2M0 BASE ALL
               2924 REF 001 V5R2M0)  OBJTYPE(*PRODUCT)
             OBJ(DSTSYSLIB/DSTLP)  STGLOC(*STD)
             VERSIONATR(*UNSPEC *ORDCHAR *ORDCHAR *ORDCHAR
               *ORDCHAR *ORDCHAR *ORDCHAR *STI *ORDDEC *ORDCHAR)
             MATCHATR(*MATCH *NOMATCH *NOMATCH *NOMATCH *NOMATCH
               *NOMATCH *NOMATCH *MATCH *NOMATCH *NOMATCH)
             TEXT('Distribution System Base Product V1R2M0')

This command adds an entry for a product to the distribution catalog and points to the save file DSTLP in the library DSTSYSLIB.

Example 6: Adding a Distribution Catalog Entry for License File Pointing to Distribution Repository

ADDDSTCLGE   GLBNAME(COMPANY1 ACCOUNT LICENSES)
             OBJTYPE(*LICKEY)  OBJ(ACCNTLIB/ACCLICF)
             MBR(*FIRST)  STGLOC(*DSTRPS)
             TEXT('License file for ACCOUNT product')

This command adds a distribution catalog entry that is stored in the distribution repository. The license file was previously generated running the DSPLICKEY command to obtain the existing licenses keys for the product ACCOUNT from the license repository.

Example 7: Adding a Distribution Catalog Entry for License File Pointing to i5/OS Standard Location

ADDDSTCLGE   GLBNAME(COMPANY2 PURCHASE V3 LICKEYS)
             OBJTYPE(*LICKEY)  OBJ(PURCHLIB/PURCHLICF)
             STGLOC(*STD)  MBR(V3LIC)

This command adds an entry in the distribution catalog pointing to the PURCHLIB/PURCHLICF in i5/OS standard location. The license file can or cannot exist at this time.

Example 8: Adding a Distribution Catalog Entry for Stream File

ADDDSTCLGE   GLBNAME(STREAM FILE CATALOG EXAMPLE)
             OBJTYPE(*STMF)  STMF('/Dir1/Dir2/Dir3/UsrFile')
             STGLOC(*DSTRPS)
             TEXT('User file cataloged as stream file')

This command adds a distribution catalog entry to the repository that points to a stream file that is to be loaded in the distribution repository.

Example 9: Adding a Distribution Catalog Entry for Stream File with Symbolic Link

ADDDSTCLGE  GLBNAME(STREAM FILE WITH SYMBOLIC LINKS CATALOG
            EXAMPLE) OBJTYPE(*STMF)  STMF('FileLink')
            STGLOC(*DSTRPS)
            TEXT('Catalog a stream file using symbolic links')

This command adds a distribution catalog entry that points to a stream file stored in the distribution repository. However, in this example, the stream file is referred with a symbolic link. An assumption made in this example is that the current directory contains the following symbolic link:

FileLink = /SomeDirectory/SomeFile

For information about symbolic links, see the Integrated File System Introduction topic in the Information Center.

Example 10: Adding a Distribution Catalog Entry for a Stream File using *MDDATE and *MDTIME on a remote change control server.

These tokens are useful when you catalog files that are distributed regularly, such a transaction logs or sales data. For example, if you want to retrieve a transaction log from the remote change control client (remote target) on a daily basis, you can catalog it on the remote change control server where the remote change control client is attached to with a global name such as:

ADDDSTCLGE   GLBNAME(EURO TRANSACT LOG *MDDATE *MDTIME)
             OBJTYPE(*STMF) OBJ('/transact/logfile')
             STGLOC(*STD)
             VERSIONATR(*UNSPEC *ORDCHAR *ORDCHAR *ORDDATE
               *ORDTIME)  TEXT('Transaction log file')

When displaying the catalog entry it will appear as:

EURO.TRANSACT.LOG.&DATE.&TIME

To retrieve the file, you can add the next change request activity in the local system:

ADDCRQA   CRQD(QGPL/CRQDRTV)  ACTIVITY(ACT01)  ACTION(*RTV)
          GLBNAME(EURO TRANSACT LOG *MDDATE *MDTIME)
          CPNAME(RMTSRV RMTCLT)

When the change request is submitted in the local system, the remote change control client returns the global name with the *MDDATE and *MDTIME tokens expanded to the actual date and time the file was last modified. For example, if the local file was last modified on 27 February 2001 at 15:40:00, the global name returned from the change control client is:

EURO.TRANSACT.LOG.Y2001M02D27.H15M40S00

The local system (the one to which you retrieved the file) catalogs the file under this name. This way, you can retrieve the same file every day, and each copy is cataloged under a different name. You can see the date and time of the file easily from the catalog entry.

Example 11: Adding a Distribution Catalog Entry for a Stream File using *SERVER and *TARGET tokens.

These tokens are used so that one catalog entry can be used for a file on multiple change control clients (targets). The following catalog entry is added in the change control server named "FREDSWS FREDSWS":

ADDDSTCLGE   GLBNAME(EURO SALES FILE *SERVER *TARGET)
             OBJTYPE(*STMF)
             STMF('/targetdir/sales/sales.file')
             STGLOC(*STD)  TEXT('Clients sale file')

The change control server "FREDSWS FREDSWS" has two change control client (targets) attached: the change control client "FREDSWS ROSE" and "FREDSWS NORA", and the file '/targetdir/sales/sales.file' exists on both targets.

If a user at another SNA distribution services node retrieved the sales files for all the targets attached to the change control server FREDSWS by requesting the global name EURO SALES FILE *SERVER *TARGET, that user would receive the global names EURO SALES FILE FREDSWS ROSE and EURO SALES FILE FREDSWS NORA

If a user at another SNA distribution services node retrieved it from the change control server "FREDSWS FREDSWS", he would receive the global name EURO SALES FILE FREDSWS FREDSWS. Also, sending the file pointed by EURO SALES FILE *SERVER *TARGET to a focal point from the i5/OS change control server "FREDSWS FREDSWS" would result in catalog entry EURO SALES FILE FREDSWS FREDSWS sent.

Error messages

*ESCAPE Messages

MSS005B

Storage limit exceeded.

MSS0116

Maximum global name length exceeded.

MSS0117

Global name token &3 not valid. Reason code &4.

MSS0118

Global name token &3 not valid. Reason code &4.

MSS0123

Internal processing error occurred.

MSS0124

Error while managing distribution catalog.

MSS0132

Catalog entry already exists for object &1.

MSS0133

Not authorized to add distribution catalog entry.

MSS0135

Distribution catalog entry not added.

MSS0136

Global name already exists.

MSS0137

Distribution catalog entry not added.

MSS0138

Object, file member, folder or document does not exist.

MSS0139

Library *LIBL not valid when local storage location is *STD.

MSS013A

Member *FIRST not valid when local storage location is *STD.

MSS013B

Catalog entry already exists for document &1.

MSS013C

Catalog entry already exists for the folder.

MSS013D

Object not loaded into distribution repository.

MSS014E

Value &2 for OBJ is more than 8 characters.

MSS014F

&1 is not an installable object.

MSS0185

Stream file not loaded into distribution repository.

MSS0188

Catalog entry already exists for the stream file.

MSS019B

Description for object &1 not found.

MSS019D

Folder description not found.

MSS01A1

Object type &2 not supported.

MSS01A6

Global name format is only valid for IBM i products.

MSS01A7

Target release in global name token &4 not supported.

MSS01A9

Stream file not found.

MSS01AA

Stream file cannot be accessed. Reason code &1.

MSS01D2

File not cataloged.

MSS01D5

Match attribute &4 for token &3 not valid.

MSS01D6

Length of global name token &3 not valid.

MSS01D7

Value of global name token &3 not valid.

MSS01D8

Global name not valid.

MSS01DA

Version attribute &4 for token &3 not valid.

MSS01E1

Library must be QSYS or *LIBL.

MSS01FB

Object specified does not contain a product.

MSS01FC

Global name not valid for product.

MSS01FE

Target release &1 not valid.