ADDCCSCLT (Add Change Control Server Client)

Note: To use this command, have the 5722-MG1 (Managed System Services for iSeries) licensed program installed.

ADDCCSCLT Command syntax diagram

 

Purpose

The Add Change Control Server Client (ADDCCSCLT) command allows the user to define a client to be recognized by the Change Control Server. This command should be used to define the first client to the change control server.

 

Required Parameters

CLIENT

Specifies the name of the client being added.

client-name: Specify a maximum of 63 characters for the name of the client. The name of the client must be precisely specified. Embedded blanks are not allowed. If you specify the name of an existing client, the command is rejected. The following characters are not allowed: asterisk (*), question mark (?), and slash (/).

CPNAME

The control point name for this client. This is the control point part of the SNA distribution services address. NetView/DM refers to this field as the target address.

control-point-name: Specify the APPN control point name of the client being added. A maximum of 8 characters can be used in this field. Both letters and numbers are allowed. Embedded blanks are not allowed. If any lowercase characters are specified, the system changes them to and stores them as uppercase characters.

 

Optional Parameters

CLTMODE

The mode in which the change control client is configured. The possible values are:

*PUSH: The change control client is configured with push mode. Change control and distribution operations on a change control client that is configured with push mode are controlled from a change control server in the network. A push mode change control client cannot intervene in the operations performed on it. This mode is allowed when the value of the Client Type (CLTTYPE) parameter is *CLIENT, *SERVER, or *SINGLE.

*FOCAL: The change control client is configured as a focal point. A change control client configured in this mode receives change control reports from change control clients for which it is defined as the focal point. Reports are routed to the focal point even if operations are initiated from another change control client in the network. A focal point can be considered a focal point from a remote change control client. This value is valid when the value of the Client Type (CLTTYPE) parameter is *SERVER or *SINGLE. When the change control client is configured as a focal point, it is recognized as a remote change control client. Only one client can be identified as the focal point.

*PULL: The change control client is configured with pull mode. Change control operations on a pull mode change control client can be controlled either by the change control client itself, or by a change control server in the network. This mode is allowed when the value of the Client Type (CLTTYPE) parameter is *CLIENT, *SERVER, or *SINGLE.

*MANAGER: This change control client is configured as a manager. A change control client that is configured in manager mode can perform change control operations on any change control client inside its domain. It also receives change control reports from those change control clients for which it is defined as manager. This mode is allowed when the value of the Client Type (CLTTYPE) parameter is *SERVER or *SINGLE. When the change control client is configured as a manager, it is recognized as a remote change control client.

*NOMODE: The change control client is a user interface only. This mode must be used when the value of the Client Type (CLTTYPE) parameter is *UI (user interface).

CLTTYPE

The type of client that you are defining.

*CLIENT: The change control client is configured as a client type. A change control client is of client type when it is working in conjunction with a change control server and has the Software Distribution Client product installed. All local or remote change control clients must be configured. Remote change control clients must be configured if they are to send or receive files or change control requests. Change control operations can be performed on remote change control clients if the remote administration product option is installed on your system. You do not need to configure a remote change control client to receive distributed files or change control commands from it. Up to 2024 local change control clients can be defined for a change control server. This value is only valid when CLTMODE(*PUSH) or CLTMODE(*PULL) is specified.

*SERVER: The change control client is configured as a server type. Change control clients that have the Software Distribution Server option installed are configured as servers. The Software Distribution catalog resides at a change control server, and change control and distribution operations for a change control domain are initiated from them. A change control server can initiate change control operations to remote change control clients if the Remote Administration product option is installed on it. This value is valid for CLTMODE(*PUSH), CLTMODE(*PULL), CLTMODE(*MANAGER), and CLTMODE(*FOCAL).

*SINGLE: The change control client is configured as single-node type.Change control clients that are running Software Distribution and are configured as a base system can be configured as single-node change control clients. Single-node change control clients can be used as preparation sites for software or as focal points to received reports of change control operations. NetView/DM for MVS nodes must be defined as single-node change control clients. This value is valid for CLTMODE(*PUSH), CLTMODE(*PULL), CLTMODE(*MANAGER), and CLTMODE(*FOCAL).

*UI: The change control client is configured as user-interface type. These change control clients can only be used to run the Software Distribution user interfaces. This type of change control client is useful when you have an environment with more than one change control server. It allows an administrator to access all change control servers from the same change control client either to perform administrative tasks or to schedule distributions to change control clients. A workstation configured as a user-interface change control client is used to initiate change control on other change control clients, or to request distributions to and from the change control server. User interface change control clients cannot receive change control instructions from a change control client. This value is valid when CLTMODE(*NOMODE) is specified.

SVRNAME

Specifies the name of the change control server that the remote change control client is connected to. This parameter is required if the change control client is remote or if CLTTYPE(*CLIENT) is specified.

*DFT: The name of the change control server to which the change control client is physically connected.

server-name: The name of the change control server to which the change control client is connected. If the name you specify is different from the name of the local server, the client is configured as a remote client.

The server name can be up to 63 characters. Valid server names consist of uppercase letters A through Z, numbers 0 through 9, and special characters: at sign (@), dollar sign ($), and the number sign (#). The asterisk (*), question mark (?), and slash (/) characters are not allowed.

DMNID

Specifies the change control server domain identifier of the change control client being added. This parameter is not valid when CLTTYPE(*UI) is specified and the change control client is rmeote, or when the change control client is local. This parameter is reqiured if CLTMODE(*MANAGER) or CLTMODE(*FOCAL) is specified. The possible values are:

*SVRCPNAME: The control point name of the client. If CLTTYPE(*CLIENT) is specified, the domain identifier is set to the control point name of the change control server to which the change control client is connected. if CLTTYPE(*SERVER) or CLTTYPE(*SINGLE) is specified, the domain identifier is set to the value specified in the control point name (CPNAME) parameter.

domain-identifier: Specifies the change control server domain identifier of the change control client being added. The domain identifier can be a maximum of 8 characters. Valid domain identifiers consist of uppercase letters A through Z, numbers 0 through 9, and special characters: at sign (@), dollar sign ($), and the number sign (#).

OPSYSTYPE

Defines the operating system type of the client being defined. Some of the products or names listed may be trademarks or service marks of other companies.

*OS/2: Client running NetView Distribution Manager Agent/2.

*AIX: Client running NetView Distribution Management Agent/6000.

*DOS: Client running NetView Distribution Management Agent for DOS.

*HPUX: Client running NetView Distribution Management Agent for HP-UX.

*IRIX: Client running NetView Distribution Manager Agent for IRIX.

*MAC: Client running NetView Distribution Management Agent for MAC.

*MVS: Client running NetView Distribution Manager Agent for MVS.

*NCR: Client running NetView Distribution Management Agent for NCR.

*NETWARE: Client running NetView Distribution Manager Agent for Netware.

*OS/2: Client running NetView Distribution Manager Agent/2.

*OS400: Client running Managed System Services for iSeries.

*SCO: Client running NetView Distribution Management Agent for SCO.

*SINIX: Client running NetView Distribution Management Agent for SINIX. SINIX is a product of Siemens Nixdorf company.

*SOLARIS: Client running NetView Distribution Management Agent for Sun Solaris. Sun Solaris is a SunSoft product and is a trademark of SUN Microsystems, Incorporated.

*SUNOS: Client running NetView Distribution Management Agent for SunOS. SunOS is a trademark of SUN Microsystems, Incorporated.

*WINDOWS: Client running NetView Distribution Management Agent for Windows.

*WINDOWS95: Client running NetView Distribution Manager Agent for Windows 95.

*WINDOWSNT: Client running NetView Distribution Management Agent for Windows/NT. Windoes NT is a trademark of Microsoft Corporation.

TEXT

A description of the client being defined.

*NONE: No text is specified.

description: Specify a maximum of 59 characters for the description of the client.

CCPERIOD

Specifies a period of time allocated for change control requests. This parameter is not valid when CLTTYPE(*UI) is specified. This parameter is ignored when the change control client is remote.The following values can be coded in this parameter, which contains a list of two elements:

Element 1: Starting Time

One of the following is used to specify the starting time at which change control operations can be performed on the client.

*FIRST: The change control operations can start at first time of day. For example, you can specify 24:01.

start-time: Specify the starting time at which change control operations can be started. Specify the time using hours and minutes.

The time can be specified as 4 or 6 digits (hhmm or hhmmss, where hh = hours, mm = minutes, and ss = seconds). Seconds are optional. The time can be specified with or without a time separator, such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).

Element 2: Ending Time

One of the following is used to specify the ending time at which change control operations will stop on the client.

*LAST: The change control operations can stop at last time of day. For example, you can specify 23:59.

stop-time: Specify the ending time at which change control operations will stop. Specify the time using hours and minutes.

The time can be specified as 4 or 6 digits (hhmm or hhmmss, where hh = hours, mm = minutes, and ss = seconds). Seconds are optional. The time can be specified with or without a time separator, such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).

DSTPERIOD

Specifies a period of time allocated for distribution requests. This parameter is not valid when GLTTYPE(*UI) is specified. This parameter is ignored when the change control client is remote. The following values can be coded in this parameter, which contains a list of two elements:

Element 1: Starting Time

One of the following is used to specify the starting time at which distribution operations can be performed on the client.

*FIRST: The distribution operations can start at first time of day.

start-time: Specify the starting time at which distribution operations can be started. Specify the time using hours and minutes.

The time can be specified as 4 or 6 digits (hhmm or hhmmss, where hh = hours, mm = minutes, and ss = seconds). Seconds are optional. The time can be specified with or without a time separator, such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).

Element 2: Ending Time

One of the following is used to specify the ending time at which distribution operations will stop on the client.

*LAST: The distribution operations will stop at last time of day.

end-time: Specify the ending time at which distribution operations will stop. Specify the time using hours and minutes.

The time can be specified as 4 or 6 digits (hhmm or hhmmss, where hh = hours, mm = minutes, and ss = seconds). Seconds are optional. The time can be specified with or without a time separator, such as a colon (:). With a time separator, specify a string of 5 or 8 digits (hh:mm or hh:mm:ss).

MSGLOGLVL

Message log level defines the log level that should be used by change control clients before they establish a connection to the change control server and discover the level configured for them. This parameter is ignored when the change control client is remote.

*NORM: This is the default log level and includes both errors and messages about the main or normal events such as the acceptance of a change management request.

*MIN: This value should only be selected if there are problems with excess logging on the system. At this level, error logs with the minimal amount of information are produced. Fatal errors are always logged.

*DIAG: This value should only be selected if a collection of logs is being performed for helping to solve a problem. When you specify this value, detailed information about the change control server process is reported.

CUSTOMER

The name of the customer at the client. This name is used when it is necessary to contact the customer.

*NONE: No customer name is specified.

customer-name: Specify a maximum of 59 characters for the name of the customer. The customer name can be specified in any format appropriate to the user.

CONTACT

Specifies the name of the person that service personnel on the change control client enterprise should contact.

*NONE: No contact name is specified.

contact-name: Specify a maximum of 59 characters for the name of the contact. The contact name can be specified in any format appropriate to the user.

ADDRESS

Specifies the street address, city, state, country, and zip code of the change control client enterprise.

*NONE: No address is specified.

contact-address: Specify a maximum of 199 characters for the address for the specified client. The contact address can be specified in any format appropriate to the user.

MANAGER

Specifies the name of the person who is the manager on the change control client enterprise.

*NONE: No owning manager is specified.

owning-manager: Specify a maximum of 59 characters for the name of the owning manager. The owning manager can be specified in any format appropriate to the user.

PHONE

Specifies the complete change control client enterprise telephone number. The telephone number should include the area code, exchange, number, and the extension where the service representative can reach the person to contact about system problems.

*NONE: No telephone number is specified.

telephone-number: Specify up to 31 characters for the telephone number of the client. The telephone number can be specified in any format appropriate to the user.

PASSWORD

This keyword is not available for this release.

ACCKEY

It is the client access key (TAK) value. If this value is specified, the access key must exist in the access key table and must be assigned to the user.

The possible values are:

*NONE: No client access key is specified.

access-key: Specify an access key to be assigned to the client. This is a four-byte binary field.

HDWPARM

The definition of a hardware parameter that is used for checking hardware prerequisites when installing a change file. Up to 10 hardware parameters can be specified. This parameter is not valid when CLTTYPE(*UI) is specified. This parameter is ignored when the change control client is remote.

*NONE: No hardware parameters are specified.

Element 1: Parameter

hardware-parameter: Specify a maximum of 80 characters for the hardware parameter.

Element 2: Value

value: Specify a maximum of 80 characters for the value of the hardware parameter.

INSTKN

An installation token to be used by the client during change file installation. An installation token should be the directories that will contain the files and paths that will be installed with the product on the change control client. Up to 10 installation tokens can be specified. This parameter is not valid when CLTTYPE(*UI) is specified.

*NONE: No installation tokens are specified.

Element 1: Token

installation-token: Specify a maximum of 11 characters for the installation token.

Element 2: Value

value: Specify the a maximum of 49 characters for value of the installation token parameter.

RMTLOCNAME

Specifies the address and address type of the client to be added. This parameter is ignored when the change control client is remote.

Element 1: Client address

The client address can be an internet protocol host name, an internet address, or an SNA network ID and control point name.

The following elements can be used in this parameter:

*CLIENT: The client address will be set to the value specified in the client name (CLIENT) keyword. If this value is specified then *IP should be specified as the address type. The value specified in the client name (CLIENT) keyword will be validated as an Internet or host name address.

*CPNAME: The control point name will be set to value specified in the control point name (CPNAME) keyword and the network ID will be set to the control point name assigned to the change control server. If this value is specified then *SNA should be specified as the address type.

remote-location-name: Specify an Internet Protocol host name, an Internet address, or an SNA network ID and control point name.

• A host name must follow these conventions:

  • The first character must be either an English alphabetic character or a numeric character.
  • The last character must be either an English alphabetic character or a numeric character.
  • Blanks ( ) are not allowed.
  • The special characters, period (.) and minus (-), are allowed.
  • Parts of the name separated by periods (.) cannot exceed 63 characters in length.
  • Internet address names (in the form nnn.nnn.nnn.nnn) are not allowed.
  • Names must be from 1 to 255 characters in length.

• The internet address is specified in the form nnn.nnn.nnn.nnn, where nnn is a decimal number ranging from 0 through 255. An internet address is not valid if it has a value of all binary ones or all binary zeros for the network identifier (ID) portion or the host name portion of the address. If the internet address is entered from a command line, the address must be enclosed in apostrophes.
• An SNA client address is specified using the format nnnnnnnn.cccccccc, where nnnnnnnn is the network ID and cccccccc is the control point name. If only the control point name, cccccccc is specified, the network ID will be set to the control point name assigned to the Change Control Server. The SNA client address can also be specified as nnnnnnnn.*CPNAME, where *CPNAME is the value specified in the control point name (CPNAME) keyword.

Element 2: Address type

The possible address type values are:

*IP: The remote location name has an Internet Protocol (IP) address type.

*SNA: The remote location name has a Systems Network Architecture (SNA) address type.

MODE

Specify the name of the mode that define the connection with the change control client. This parameter is ignored when the value of the address type keyword on the RMTLOCNAME parameter is something other than *SNA.

The possible mode values are:

*NETATR: The mode specified in the network attributes is used.

mode-name: Specify a maximum of 8 characters for the mode name. Embedded blanks are not allowed. If any lowercase characters are specified, the system changes them to and stores them as uppercase characters.

Examples for ADDCCSCLT

Example 1: Adding a client using default values

ADDCCSCLT CLIENT(KevinAldux) CPNAME(MEXGPL13)

Example 2: Adding client KevinAldux using hardware parameters, installation tokens, distribution period and password

ADDCCSCLT CLIENT(KevinAldux) CPNAME(MEXGPL13) TEXT('Client no.2') +
          DSTPERIOD('12:30:00' '16:43:00') PASSWORD()  +
          HDWPARM((MEM 16MB) (DISK 120MB) (KEYB LA)) +
          INSTKN((TOKEN1 /USR) (TOKEN2 /USR2))

Example 3: Adding client CONNERY using DOS operating system, Manager, phone, password, address, SNA client address and mode

ADDCCSCLT CLIENT(CONNERY) CPNAME(MEXGPL16) OPSYSTYPE(*DOS) +
          TEXT('Client no.3') DSTPERIOD(*FIRST '16:43:00') +
          MANAGER(Charles) PHONE('(507)285-2884') PASSWORD() +
          ADDRESS('Patria Avenue 30') +
          HDWPARM((MEM 16MB) (DISK 120MB) (KEYB LA)) +
          INSTKN((TOKEN1 /USR) (TOKEN2 /USR2)) +
          RMTLOCNAME(APPN.MEXGPL13 *SNA) +
          MODE(blank)

Example 4: Adding client Lorena with Windows/NT operating system, an internet address, message log level, hardware parameters, installation tokens, manager name, phone and password

ADDCCSCLT CLIENT(Lorena) CPNAME(MEXGPL13) OPSYSTYPE(*WINDOWSNT) +
          TEXT('Client no.4') MSGLOGLVL(*MIN) +
          MANAGER(Charles) PHONE('(507)112-2884') PASSWORD() +
          ADDRESS('Patria Avenue 30') +
          HDWPARM((MEM 16MB) (DISK 120MB) (KEYB LA)) +
          INSTKN((TOKEN1 /USR) (TOKEN2 /USR2)) +
          RMTLOCNAME('9.18.1.2' *IP)

Error messages for ADDCCSCLT

*ESCAPE Messages

MSS0A1A

Target access key not found.

MSS0A1F

Control point name &2 already exists.

MSS0A2B

Installation token not valid.

MSS0A2D

Client name specified already exists.

MSS0A29

Target access key table not found.

MSS0123

Internal processing error occurred.

MSS2102

Change control client not added.