|
|
8133
|
ERROR: Deployment plan group groupname specifying PAKGRPNAME pakgroupname cannot be found in the Application Package. |
|
|
Description
|
One GROUPS entry with PAKGRPNAME specified indicates this group is associated with one of the Application Package instance groups whose name is the PAKGRPNAME parameter value. If this group is not specified in the Applicatoin Package Properties.xml file, the tmcrdom command reports this error.
|
|
Action
|
Specify PAKGRPNAME with the value which is an existing group name in the Applicatoin Package Properties.xml file.
|
|
|
|
8135
|
ERROR: Deployment plan *RMS entry rmsname cannot be found in corresponding Application Package. |
|
|
Description
|
One *RMS entry with PAKRMID specified indicates the rms entry is associated with one of the Applicatoin Package instance rms entries whose RMID is the PAKRMID parameter value. If this rms entry is not specified in the Applicatoin Package Properties.xml file, the tmcrdom command reports this error.
|
|
Action
|
Specify PAKRMID with the value which is an existing *RMS entry RMID in the Applicatoin Package Properties.xml file.
|
|
|
|
8137
|
ERROR: Deployment plan SERVER entry servername with SRVID number cannot be found in corresponding Application Package. |
|
|
Description
|
One SERVERS entry with PAKSRVID specified indicates this server entry is associated with one of the Applicatoin Package instance SERVERS entries whose SRVID is the PAKSRVID parameter value. If this SERVERS entry is not specified in the Applicatoin Package Properties.xml file, the tmcrdom command reports this error.
|
|
Action
|
Specify PAKSRVID with an existing SERVERS entry SRVID value in the Applicatoin Package Properties.xml file.
|
|
|
|
8140
|
ERROR: Deployment plan SERVICE entry servicename with SRVGRP groupname cannot be found in corresponding Application Package. |
|
|
Description
|
One SERVICES entry belonging to a group that has PAKNAME specified indicates this service entry is associated with one of the Applicatoin Package instance SERVICES entries whose name is the same with this service. If this SERVICES entry is not specified in the Applicatoin Package Properties.xml file, the tmcrdom command reports this error.
|
|
Action
|
Specify the service name with an existing SERVICES entry name value in the Application Package Properties.xml file.
|
|
|
|
8141
|
ERROR: The number of groups with same PAKNAME packagename and INSTANCE number is not equal to the number of the Application Package. |
|
|
Description
|
Once an Application Package instance, specified by PAKNAME and INSTANCE parameters, is associated with groups defined in the deployment plan, all groups in the Application Package Properties.xml file must be associated with groups in the deployment plan. This means, the number of groups in the deployment plan with the same PAKNAME and INSTANCE values must be exactly equal to the number of groups in the Application Package Properties.xml file.
|
|
Action
|
Make sure all groups in the Application Package Properties.xml file are associated in the deployment plan file.
|
|
|
|
8142
|
ERROR: The number of *RMS entries belonging to a group with PAKNAME packagename and INSTANCE number is not equal to the number of the Application Package. |
|
|
Description
|
Once an Application Package instance, specified by PAKNAME and INSTANCE parameters, is associated with some of the groups defined in the deployment plan, groups in the Application Package Properties.xml file must be associated with groups in the deployment plan. This means, the number of groups in the deployment plan with the same PAKNAME and INSTANCE values must be exactly equal to the number of groups appears in the Application PackageProperties.xml file. Similarly, the number of *RMS entries in the deployment plan belonging to these groups with same PAKNAME and INSTANCE values, must be exactly equal to the number of *RMS entries in the Application Package Properties.xml file.
|
|
Action
|
Make sure all the *RMS entries in the Application Package Properties.xml file are associated in the deployment plan file.
|
|
|
|
8143
|
ERROR: The number of SERVERS entries belonging to a group with PAKNAME packagename and INSTANCE number is not equal to the number of the Application Package. |
|
|
Description
|
Once an Application Package instance, specified by PAKNAME and INSTANCE parameters, is associated with groups defined in the deployment plan, all groups in the Application Package Properties.xml file must be associated with groups in the deployment plan. This means, the number of groups in the deployment plan with the same PAKNAME and INSTANCE values must be exactly equal to the number of groups appears in the Application Package Properties.xml file. Similarly, the number of SERVERS entries in the deployment plan belonging to these groups with same PAKNAME and INSTANCE values, must be exactly equal to the number of SERVERS entries in the Application Package Properties.xml file.
|
|
Action
|
Make sure all the SERVERS entries in the Application Package Properties.xml file are associated in the deployment plan file.
|
|
|
|
8144
|
ERROR: The number of SERVICES entries belonging to a group with PAKNAME packagename and INSTANCE number is not equal to the number of the Application Package. |
|
|
Description
|
Once an Application Package instance, specified by PAKNAME and INSTANCE parameters, is associated with some of the groups defined in the deployment plan, all groups in the Application Package Properties.xml file must be associated with groups in the deployment plan. This means, the number of groups in the deployment plan with same PAKNAME and INSTANCE values must be exactly equal to the number of groups appears in the Application Package Properties.xml file. Similarly, the number of SERVICES entries in the deployment plan belonging to these groups with same PAKNAME and INSTANCE values, must be exactly equal to the number of SERVICES entries in the Application Package Properties.xml file.
|
|
Action
|
Make sure all the SERVICES entries in the Application Package Properties.xml file are associated in the deployment plan file.
|
|
|
|
8152
|
ERROR: Domain domainname existes in the DEPREPOSITORY %s. |
|
|
Description
|
It shows this domain is previously created in the DEPREPOSITORY and has not been deleted.
|
|
Action
|
Use tmdeldom command to delete this domain before creating it. Using tmdeldom with -f option can force delete the domain from the DEPREPOSITORY.
|
|
|
|
8195
|
ERROR: The AOUT parameter aoutpath for server servername must be <= len characters in length. |
|
|
Description
|
The AOUT parameter in the Application Package Properties.xml file is a relative path to the Application Package. In the generated UBBCONFIG file, you must change it to the relative APPDIR path. AOUT changes to ApplicationPackageName/AOUT. If the new path length is larger than 256, tmcrdom reports this error.
|
|
Action
|
Decrease the path length of directory or AOUT.
|
|
|
|
8196
|
ERROR: The ENVFILE parameter envfilepath for server servername must be <= len characters in length. |
|
|
Description
|
The ENVFILE parameter in Application Package Properties.xml file is a relative path to the Application Package. In the generated UBBCONFIG file, you must change it to the absolute path. ENVFILE changes to APPDIR/ApplicationPackageName/ENVFILE. If the new path length is larger than 256, tmcrdom reports this error.
|
|
Action
|
Decrease the path length of directory or ENVFILE.
|
|
|
|
8197
|
ERROR: The RCMD parameter rcmdpath server servername must be <=len characters in length. |
|
|
Description
|
The RCMD parameter in Application Package Properties.xml file is a relative path to the Application Package. In the generated UBBCONFIG file, you must change it to the absolute path. RCMD changes to APPDIR/ApplicationPackageName/RCMD. If the new path length is larger than 256, tmcrdom reports this error.
|
|
Action
|
Decrease the path length of directory or RCMD.
|
