Attempting to run a batch of uploads via GuardIEn. I normally run batch uploads via a cygwin script. I have configured a batch script to start a cygwin session to run the batch upload (basically same script I run directly). On a test server this works fine however on the production server I get the following error:
ParmClient::GetMDParms failure, mdsrc = 28322
I cannot find any reference to the exact error, I'm assuming it's trying to read environment variables and cannot find them. I've hardcoded all the IEF_xxx variable in cygwin and exported them so they should be accessible. I've also added them to the command line using -p & -g without success as follows:
upload -u CSEADMIN -t APPLY -d DIRECTORY_NAME -p CSE_HOSTNAME/2500 -g ENCY87
Could you advise the exact meaning of the error being returned and any possible solution?
Release : 8.6
Component : CA Gen Client Server Encyclopedia
The error "ParmClient::GetMDParms failure, mdsrc = 28322" is not documented but does related to a problem with missing or incorrect values for Environment Variables.
Support tested an upload with "-t APPLY" with a .cmd script (not Cygwin, but should be the equivalent), where all IEF and CSE environment variables were set to no value and used similar command syntax i.e. the .cmd file contains:
upload -u encyadmn -t APPLY -d DIRECTORY_NAME -p lvntest014852/2500 -g ENCY > upload.out 2>&1
The output file upload.out showed a successful upload.
However, if an incorrect group name is used for the "-g" parameter then the upload.out file showed the reported error "ParmClient::GetMDParms failure, mdsrc = 28322"
(NOTE: If an incorrect hostname or port number is used then error "ParmClient::StartClient failure, mdsrc = 29008" occurs instead.)
The CSE Server Software Group name can be checked with the CSE Coordination Client using menu option Encyclopedia > Actions > Open:
CA Gen 8.6 > Encyclopedia > Client Server Encyclopedia > Client Server Encyclopedia Clients > Client Server Encyclopedia Coordination Client > Encyclopedia Selection Window > Actions in Coordination Client
It was confirmed that that group name ENCY87 being used did not match the Production CSE Software Group name and correcting the "-g" parameter value fixed the problem.
NOTE: The Software Group Name value was also being reset within GuardIEn to an incorrect value, so that also had to be changed.
Using environment variables instead of command line parameters and having an incorrect value for IEF_ENCYGROUP would also cause the same error.