Page tree
Skip to end of metadata
Go to start of metadata

Article State

Approved

Article Number

KB-20180412144355

Product

mainstorconcept mzHOST
Summary

Language

EN

DE

Issue

Troubleshooting Guide

Cause

MZH100E Error Collecting machine information. RC=12

mzHost is unable to gather information regarding this machine. The mzHost started task will terminate

Solution

Ensure the MZHOST_HOME/com/msc/mzhost/zos directory is APF authorized, as described in the mzHost Administration Guide

If the problem persists contact mainstorconcept GmbH for further assistance.

 

MZH101E mzHOST was interrupted while collecting machine information. RC=12

mzHost was unable to finish gathering information regarding this host system. The mzHost started task will terminate

Solution

Ensure no RACF changes were applied to the surrogate user id associated with the mzHost started task when this error was reported.

If the problem persists contact mainstorconcept GmbH for further assistance.

 

MZH102E License for mzhost has expired. Please contact Mainstorconcept Sales Support to continue using this Software. RC=12

the License for mzHost on this LPAR is no longer valid as it has reached the purchased end date. Please contact mainstorconcept GmbH for assistance in buying a new License for your host.

Solution

Please contact mainstorconcept GmbH for assistance in buying a new License for your host.

 

MZH104W License for mzHost will expire in 999 days. Please contact mainstorconcept Sales Support to continue using this Software.

The mzHost License will expire in less than 7 days.

Solution

Contact mainstorconcept GmbH Sales Support to renew your license.

 

MZH105E Error opening temp data file area. mzHost will terminate. RC=12

mzHost is unable to setup a temporary data file area.

Solution

Consult the mzHost Administration guide regarding RACF permissions or contact mainstorconcept GmbH Technical Support for further assistance

 

MZH106E Error reading temp data file area. mzHost will terminate. RC=12

mzHost is unable to read from the temporary data file area.

Solution

Consult the mzHost Administration guide regarding RACF permissions or contact mainstorconcept GmbH Technical Support for further assistance

 

MZH107E error creating console communication pipes. Please contact mainstorconcept Technical Support. RC=12

mzHost is unable to setup the MVS communication consoles required. mzHost started task will terminate.

Solution

Ensure the MZHOST_HOME/com/msc/mzhost/zos directory is APF authorized, as described in the mzHost Administration Guide

If the problem persists contact mainstorconcept GmbH for further assistance.

 

MZH108E Error starting the MVS communication for this thread. mzHost will terminate. RC=12

The mzHost thread cannot establish communication with MVS. This is normally an APF authorization issue.

Solution

Ensure the MZHOST_HOME/com/msc/mzhost/zos directory is APF authorized, as described in the mzHost Administration Guide

If the problem persists contact mainstorconcept GmbH for further assistance.

 

MZH109E Error closing the MVS Console for this thread. Thread will terminate. RC=8

The mzHost started task was is processing the shutdown command but cannot cleanly stop communication with MVS. The thread will terminate with an error.

Solution

If a command was being processed, the data will be discarded and the thread will terminate with error

 

MZH110E IBM Encryption Facility unable to process request. RC=12

The encryption facility is unable to decode the license file provided. The mzHost started task will terminate.

Solution

Consult the mzHost Administration Guide regarding the setup for the encryption facility.

If the problem persists, contact mainstorconcept or the assistance.

 

MZH111E mzHost License NOT found. RC=12

The mzHost license file is missing. The mzHost started task will terminate

Solution

Upload the mzHost.lic file as instructed in the mzHost_License_Readme.txt file.

 

MZH112E Unable to process the mzHost license information. RC=12

The mzHost license file is not the in the correct format and cannot be processed. The mzHost started task will terminate.

Solution

Upload the mzHost.lic file as instructed in the mzHost_License_Readme.txt file.

 

MZH113E Identified Host CPU does not comply with the licensed machine for this software. RC=12

The host machine running this mzHost started task is not the one described in the license uploaded. The mzHost started task will terminate.

Solution

Ensue the mzHost license information provided was correct and that the mzHost license has been installed on the correct machine/lpar.

 

MZH114E Identified Host Machine Type does not comply with the licensed machine for this software. RC=12

The host machine running this mzHost started task is not the one described in the license uploaded. The mzHost started task will terminate.

Solution

Ensue the mzHost license information provided was correct and that the mzHost license has been installed on the correct machine/lpar.

 

MZH115E Error communicating with MVS system. RC=12

mzHost is unable to communicate with MVS.

Solution

Consult the mzHost Administration Guide regarding the setup for the surrogate userid.

If the problem persists, contact mainstorconcept or the assistance.

 

MZH116E mzHOST was interrupted while communicating with MVS. RC=8

mzHost was interrupted while communicating with MVS.

Solution

The started task may have been processing a shutdown command while processing a request.

If the problem persists, contact mainstorconcept Technical Support for assistance.

 

MZH117E MZPEER member not found in INPARM DD. RC=8

The MZPEER file/DD was not found while setting up mzHost.

Solution

Refer to the mzHost Administration Guide regarding the MZPEER, MZSERVER and MZCLIENT files.

 

MZH118W MZSERVER member not found. The mzHost Server will be started with DEFAULT values set. RC=4

MZSERVER member/file was not found. Default values will apply.

Solution

Refer to the mzHost Administration Guide regarding the MZPEER, MZSERVER and MZCLIENT files.

The started will not terminate.

 

MZH119E INPARM DD not found. mzHost started task will terminate. RC=12

Only applicable to mzHost for zOS. The INPARM DD was not found in the started task JCL used for this instance of mzHost.

Solution

Refer to the mzHost Administration Guide.

 

MZH120E INPARM DD could not be processed. mzHost started task will terminate. RC=12

mzHost DD could not be processed. mzHost will terminate

Solution

Refer to the mzhost Administration Guide for information regarding the setup of the INPARM DD.

 

MZH121W SRVNAME is not defined, using default name MZHOST. RC=4

The MZSERVER file did not specify a Server name. This will not cause the mzHost started task/application to terminate.

Solution

The Default name MZHOST will be used. Administrators can edit the name at any time and restart the started task as normal.

 

MZH122W SRVIP is not defined, using default definition 127.0.0.1

The MZSERVER file did not specify a Server IP, the default IP address (local 127.0.0.1 will be used.

This will not cause the mzHost started task to terminate but may cause issues if this was not the intended IP address.

Solution

The Default name MZHOST will be used. Administrators can edit the name at any time and restart the started task as normal.

 

MZH123W SRVPORT is not defined, using default definition 61515. RC=4

MZSERVER file did not specify a port number for the mzHost Server, the default port 61515 will be used. The mzHost started task will not terminate.

Solution

The mzHost application will continue to operate as long as the default port is not already defined for another applications use.

Edit the MZSERVER member with the correct port number, save and restart the mzHost application.

 

MZH124W CLTIP is not defined, using default definition 127.0.0.1. RC=4

The IP address for the MZCLIENT was not specified in the MZCLIENT file/member. The default IP address 127.0.0.1 will be used.

The mzHost application will not terminate.

Solution

In most cases the default local IP address is used, unless, due to specific network requirements, a separate IP address is required for the outgoing requests from this host machine.

If required, edit the MZCLIENT file, save the file and restart the mzHost application for started task.

 

MZH125E MZSERVER file is present but could not be processed. RC=12

The MZSERVER file was found but could not be opened. The mzHost Started task or application will terminate.

Solution

Ensure the member is not being edited by another user before trying again.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH126E MZSERVER file is present but could not be read. RC=12

The mzHost MZSERVER file/member could not be read. The mzHost application or started task will terminate.

Solution

Ensure the file is free to be read and is not assigned to another process (editing etc.).

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH127W CLTNAME is not defined, using default name MZHOST. RC=4

The MZCLIENT file did not specify a CLIENT name. This will not cause the mzHost started task to terminate.

Solution

Should a unique name be preferred, edit the MZCLIETN member/file, save and restart the MZHOST application or started task.

 

MZH128E MZCLIENT file is present but could not be processed. RC=12

The MZCLIENT file was found but could not be opened. The mzHost Started task or application will terminate.

Solution

Ensure the member is not being edited by another user before trying again.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH129E MZCLIENT file is present but could not be read. RC=12

The mzHost MZCLIENT file/member could not be read. The mzHost application or started task will terminate.

Solution

Ensure the member is not being edited by another user before trying again.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH130W PEERNAME is not defined, using default name DLMx. RC=4

The MZPEER file did not specify an ALIAS name for a Peer. This will not cause the mzHost started task or application to terminate.

Solution

The default name "DLMx" will be used where x is the position of this Peer in the list of Peers defined e.g. DLM2.

 

MZH131W PEERIP is not defined, operator will need to specify the full IP on request. RC=4

The MZPEER IP address was not specified, this means that each request will need to specify the full IP address and port when sending requests to Peers

Solution

To take full advantage of the alias function, ensure each MZPEER is defined, with a name, IP address and port in the MZPEER file/member.

Save the file and restart the mzHost application or started task.

 

MZH132W PEER is not defined, using default definition 61515. RC=4

The MZPEER port was not defined in the MZPEER file or member. The default port 61515 will be used.

Solution

If the MZPEER has a different port defined to the default port, the connection will fail when a request is sent.

To update the port, edit the MZPEER member/file, save and restart the mzHost application or started task

 

MZH133E MZPEER file is present but could not be processed. RC=12

The MZPEER file was found but could not be opened. The mzHost Started task or application will terminate.

Solution

Ensure the member is not being edited by another user before trying again.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH134E MZPEER file is present but could not be read. RC=12

The MZPEER file was found but could not be read. The mzHost Started task or application will terminate.

Solution

Ensure the member is not being edited by another user before trying again.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH135E License has not been processed. Contact Mainstorconcept Technical Support. RC=8

mzHost license information was not processed. This will cause the mzHost started task to terminate.

Solution

This message will have been preceded by messages in the range: MZH100E to MZH114E.

Refer to the applicable message for the appropriate solution.

 

MZH136E Unable to process the Host Machine Information. Contact Mainstorconcept Technical Support. RC=8

mzHost was unable to identify this host machine and will terminate.

Solution

This message will have been preceded by messages in the range: MZH102E to MZH114E.

Refer to the applicable message for the appropriate solution.

 

MZH137E Error processing Local Host Date Information. Contact Mainstorconcept Technical Support. RC=8

mzHost was unable to retrieve the current System Date for this machine. This will cause the mzHost started task to terminate.

Solution

This message will have been preceded by messages in the range: MZH102E to MZH114E.

Refer to the applicable message for the appropriate solution.

 

MZH138E Unable to start and/or communicate with the mzHost Server. RC=12

The mzHost Server (MZSERVER) could not be started or is not communicating.

Solution

Check for any preceding error messages that could assist with the issue.

Make sure the application is not already running.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH139E mzHostClient was not activated on mzHost-init. RC=8

The MZCLIENT was not activated when MZHOST was activated using the mzHost-init.sh command.

The command will not be processed.

Solution

If the MZCLIENT is required. Issue the mzHost-shutdown.sh command.

Reissue the mzHost-init.sh command with the -mzHostClient parameter.

 

MZH140E mzHost InputStream not available. Server cannot be started. RC=12

The communication stream used by  MZSERVER and/or the MZCLIENT is not available. No requests can be processed by the Server or the Client.

This will cause the mzHost application to terminate.

Solution

Check the error log for any preceding error messages that could assist with resolving the issue.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH141E Unable to process incoming requests through InputStream. RC=12

The input stream used by the MZSERVER and/or MZCLIENT not processing incoming requests.

Solution

Check the error log for any preceding error messages that could assist with resolving the issue.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH142E mzHOST communication has been interrupted. RC=12

The mzHost application experienced an interruption and cannot process any further requests. This will cause the mzHost application to terminate.

Solution

Check the error log for any preceding error messages that could assist with resolving the issue.

Ensure the mzHost application was not being shut down when this error occurred.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH143E Error occurred created mzhost log and/or error files. RC=12

The mzHost application could not open and/or create the required mzHost.log and mzHost. Err files in the /var/log/ directory.

Solution

Ensure the user has the correct permissions to start the mzHost application (i.e. root).

Check the system log on the DLm for any information that may be pertinent to this error.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH144E Unable to establish vtcon connectivity, mzHost Client cannot be started. RC=12

The mzHost application could not find or open the required communication file to connect with the VTCON application running on the DLm host machine.

Solution

Check the system log on the DLm for any information that may be pertinent to this error.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH145E Error Starting Socket Listener on port xxxxx Contact Tech Support. RC=12

MZSERVER is unable to startup on the specified port (xxxxx). This will cause the MZSERVER started task or application to terminate.

Solution

Ensure the correct port is assigned to mzHost and specified in the MZSERVER file or member.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH146E cannot communicate with mzClient on this host. RC=12

The MZCLIENT is not able to communicate with the MZSERVER on this machine.

Solution

Refer to the STDERR log for further information and contact mainstorconcept Technical Support for further assistance.

 

MZH147E Unable to accept any connections. Please ensure the port xxxxx is available and listening. RC=12

The MZSERVER port was started but is not accepting connections. This will cause the MZSERVER application to terminate.

Solution

Check the network settings to ensure the specified port is active and is LISTENING.

Check the error log for any further information and contact mainstorconcept Technical Support for further assistance.

 

MZH148E Communication with the Client has been interrupted. RC=12

The mzHost application cannot send requests to the MZCLIENT or processing or the client is replying with invalid data responses from the MZCLIENT.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH149E Error sending the client a response. RC=12

An error occurred while sending the client a response to a request. This error will cause the channel between this MZSERVER and the MZCLIENT at the MZPEER to terminate.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH150E Error opening the mzHost keystore Contact Tech Support. RC=12

Related to using SSL with mzHost. The mzHost application comes with a predefined keystore which cannot be opened.

Solution

Check the error log for any information that may assist with resolving the issue  and contact mainstorconcept Technical Support for further assistance.

 

MZH151E Error implementing TLS algorithm on this server. RC=12

Related to using SSL with mzHost. The mzHost application is configured to use a specific TLS/SSL algorithm which cannot be initiated at this time.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH152E mzHost certificate failure, please contact Technical Support. RC=12

Related to using SSL with mzHost. The mzHost application comes preinstalled with a self-signed trusted certificate which has failed to establish a successful connection.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH153E mzHost encountered an unrecoverable Key exception. RC=12

Related to using SSL with mzHost. The mzHost application comes with a predefined keystore which has experienced an unrecoverable error at this time.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH154E mzHost encountered a Key Manager exception. RC=12

Related to using SSL with mzHost. The mzHost application is configured to use a specific Keystore manager which has encountered an error at this time.

Solution

Check the error log for any information that may assist with resolving the issue and contact mainstorconcept Technical Support for further assistance.

 

MZH155E Command received is blank. Processing has ended for this call. RC=4

The client connected to this server sent a blank command for processing. Conversation will end.

Solution

The MZSERVER at this host is receiving blank commands for processing from PEER MZCLIENTS, ensure all users are informed as to how to use mzHost facility at their machine.

 

MZH156E userid is not assigned to resource PEER.OPER with access level update SAFerrno  SAFerrno2 SAFerrMsg SAFrc. RC=8

The MZPEER surrogate userid was not added to the PEER.OPER Resource class as described in the mzHost Administration Guide. This will cause the conversation between this MZSERVER and the PEER MZCLIENT to end.

Solution

The PEER.OPER resource was created but the surrogate userids for the PEER MZCLIENTs were not added, this causes the security check to fail.

Either remove the PEER.OPER resource from your sites Security Facility or add the MZHOST surrogate userids as described in the mzHost Administration Guide.

 

MZH157E userid password check failed SAFerrno  SAFerrno2 SAFerrMsg SAFrc. RC=8

Related to the Security Facility Feature. The mzHost surrogate userid was found but the password was not valid.

Solution

The PEER.OPER resource was created but the surrogate userids and/or password is not valid for the PEER MZCLIENTs, this causes the security check to fail.

Either remove the PEER.OPER resource from the Security Facility or add the MZHOST surrogate userids and passwords correctly, as described in the mzHost Administration Guide.

 

MZH158E Maximum Parallel peers has been reached. RC=8

To lower the risk of spoofing, the number of concurrent MZCLIENT connections to a MZSERVER is limited to 5 at a time.

Solution

Retry command for processing.

 

MZH159E IP Address for peername has not been defined. RC=4

The MZPEER file contains the MZPEER Alias Name specified in the request, however no IP address was defined with it in the MZPEER file/member.

Solution

Retry command using the full -ip xxx.xxx.xxx.xxx -port xxxx,'command' syntax or ask the System Administrator to add the IP address for the PEER in order to make use of the mzHost Alias name feature.

 

MZH160E Cannot connect to the specified host. Please check the IP address and try again. RC=12

MZCLIENT cannot establish a connection to the peer Alias or peer IP address specified in the request.

Solution

Check the IP address specified for this request. 

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH161E Invalid response received from MZHOST PEER. RC=8

The MZPEER replied with an invalid response to this request.

Solution

Check whether or not SSL is active at the target MZPEER.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH162E Error reported by MZPEER : MZPEER error response. RC=8

 The MZPEER to which this MZCLIENT is connected has reported an error.

Solution

Refer to the MZPEER error response and act accordingly.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH163E An invalid response was received from the mzHost Peer. RC=12

 The MZPEER to which this MZCLIENT is connected has suddenly ended or sent invalid data while communicating. The conversation will end

Solution

The MZPEER running at the target host may have been shutdown or terminated unexpectedly while the conversation was active.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH164E This connection timed out without a response. RC=8

 The MZPEER to which this MZCLIENT is connected has not responded in the last 7 (seven) seconds. The conversation will end.

Solution

The MZPEER running at the target host may have been shutdown or terminated unexpectedly while the conversation was active.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH165E Error communicating with the MZHOST Server at  xxx.xxx.xxx.xxx. RC=12

The channel for communication with the target MZPEER could not be established.

Solution

The MZPEER running at the target host may have been shutdown or terminated unexpectedly while the conversation was active.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH166E Incorrect number of parameters on call to mzhostClient. RC=12

This is an internal issue and should be reported to mainstorconcept Technical Support.

Solution

This is an internal issue and should be reported to mainstorconcept Technical Support.

 

MZH167E Connection Exception encountered, ending program. RC=12

The MZCLIENT was unable to connect to the target MZPEER. The conversation will not begin

Solution

Check whether or not SSL is running at the target and whether this MZCLIENT is configured to use SSL as well.

There may be preceding error messages that could assist with diagnosing the connection issue.

If the problem persists, contact mainstorconcept Technical Support for further assistance.

 

MZH168E Incorrect use of zmzhost Client. RC=8

This is an internal issue and should be reported to mainstorconcept Technical Support.

Solution

This is an internal issue and should be reported to mainstorconcept Technical Support.

 

MZH169E Cannot communicate with the specified host. RC=12

The MZCLIENT cannot send data over a channel to the target MZPEER.

Solution

Ensure the appropriate SSL settings have been configured for both the MZPEER and the MZCLIENT.

If the problem persists contact mainstorconcept Technical Support for further assistance.

 

MZH170E Error sending error message to VTCON log. RC=12

The mzHost application cannot log an error message to the VTCON console.

Solution

Refer to the System logs for DLm for any information that may assist in diagnosing this issue.

If the problem persists contact mainstorconcept Technical Support for further assistance.

 

MZH171E No Data is being returned from Console. RC=12

The MVS Console is not returning command response output to mzHost.

Solution

The MZHOST_HOME/com/msc/mzhost/zos directory must have the appropriate attributes assigned as per the mzHost Administration Guide.

The mzHost surrogate userid must have the appropriate Security permissions as per the mzHost Administration Guide.

If the problem persists contact mainstorconcept Technical Support for further assistance.

 

MZH172E internal error creating console reader. RC=12

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

Solution

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

 

MZH173E internal error starting console communication. RC=12

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

Solution

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

 

MZH174E MVS Command response sequence Error. RC=12

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

Solution

This is an internal issue, please consult mainstorconcept Technical Support for further assistance.

 

MZH175E mzHost InputStream not available for reading. Server cannot be started.RC=12

The input stream file is exists but mzHost cannot read its contents.

Solution

Empty the $mzHost_HOME/var/ diretcory and restart the mzHost Server. If the problem persists, contact mainstorconcept GmbH for technical support.

 

MZH176E mzHost Shutdown Process Encountered an error.RC=08

The mzHost Server received a shutdown command but was interrpted by a System Error.

Solution

The Server is forcibly shutdown. If this Error message persists pleae contact mainstorconcept GmbH Techinical Support.


Solution



Workaround

Notes