Explanation | One or more required parameters are not specified. | |
Action | Re-issue the command with the required parameters. Required parameters are -a (API archive file) and -p (path to deployment location). |
Explanation | The specified command is not recognized. | |
Action | Verify that the command is entered correctly. |
Explanation | The specified API archive file is not available or not readable. | |
Action | Ensure that the file exists and the file encoding is correct. |
Explanation | The specified parameter is not supported by the command. | |
Action | Valid parameters are -a (API archive file) and -p (path to deployment location). |
Explanation | The specified file name does not end with a .aar extension. | |
Action | Specify a valid API archive file that ends with a .aar extension. |
Explanation | The required package.xml file is missing in the API archive. | |
Action | Ensure that the required package.xml file that contains the API specification is included. |
Explanation | The API is successfully created on the server API path. | |
Action | The API is activated after the server restarts. |
Explanation | The API is already deployed on the server. | |
Action | Ensure that you specify the correct API archive file (a .aar file) to be deployed. Specify the -w option to overwrite an existing API. |
Explanation | The API is successfully updated on the server. | |
Action | Restart the server to reflect the update. |
Explanation | The API is successfully removed from the server API path. | |
Action | Restart the server to reflect the changes. |
Explanation | The API is not currently deployed on the server. | |
Action | Ensure that you specify the correct API archive file (a .aar file) to be undeployed. |
Explanation | The API cannot be removed from the server. | |
Action | Remove the API directory manually from server API path. Restart the server to reflect the changes. |
Explanation | The API archive file exists but it might be empty or corrupted. | |
Action | Regenerate the API archive file. Ensure that the encoding is set correctly when the file is uploaded to the z/OS system. |
Explanation | The package.xml file in the API archive file is either missing or corrupted. If the file is corrupted, the encoding might be set incorrectly during the file upload process. | |
Action | Check that the package.xml file exists, and the encoding is correct. You might need to regenerate the API archive file. Ensure that the encoding is set correctly when you upload the file to the z/OS system. |
Explanation | The API cannot be deployed, possibly due to a lack of permission or space. | |
Action | Ensure that you have the permission to read from the source location, write to the deployment location and that there is sufficient space on the disk. |
Explanation | You might not have the permission to delete files in this location. | |
Action | Ensure that you have the permission to delete files in the API deployment location. |
Explanation | The specified directory is not available. | |
Action | Ensure that the directory exists and that you have the correct access permission. |
Explanation | The package.xml file was not found in the API archive file (.aar file). | |
Action | Regenerate and deploy the new API archive file (.aar file). |