[{"solutionDetails":{"solution":{"APARNO":"RO58255","OS":"LINUX","AVAILABLE":"TRUE","CLASS":"Warning","CNFDATE":"2013-05-01T17:00:00.000Z","COMPONENTCODE":"XCLX86","DEFDATE":"2013-05-01T17:00:00.000Z","DISTRIBUTION":"AVAILABLE","GROUPNAME":"OMXCOM GBL S 1","HYPER":"false","KEYWORD":"\"\\nCOMMAND\",\"\\nINVALID\",\"\\nERROR\",\"\\nLINE\",\"\\nSEGMENTATION\",\"\\nFORMAT\",\"\\nDATE\",\"\\nTRANSFER\",\"\\nCRASH\",\"\\nSTART\",\"\\nPRODUCT\",\"\\nSIGSEGV\",\"\\nCOMMANDLINE\",\"\\nSTARTDATE\",\"\\nXCOMTCP\",\"\\nSTART_DATE\",\"\\nWRONG FORMAT\",\"\\nRO58255\",\"\\nT53S954\",\"\\nWRONG\",\"\\nHISTORY\",\"\\nRECORD\",\"\\nDATABASE\",\"\\nVALUE\",\"\\nNOT\",\"\\nDB2\",\"\\nLARGE\",\"\\nSTANDALONEUI\",\"\\nWRITTEN\",\"\\nTOO\",\"\\nAVGREC\",\"\\nODBC\",\"\\nSQLSTATE\",\"\\n22001\",\"\\nMYSQL\",\"\\nSQL0433N\",\"\\nEXTENDED\",\"\\nREPORT\",\"\\nFILE\",\"\\nEXPORT\",\"\\nATTRIBUTE\",\"\\nINCOMPLETE\",\"\\nINFORMATION\",\"\\nMISSING\",\"\\nEASYTRIEVE\",\"\\nCSV\",\"\\nGUI\",\"\\nUNICODE\",\"\\nHISTF\",\"\\nLOG\",\"\\nSTARTUP\",\"\\nBROWSER\",\"\\nDEFAULT\",\"\\nINPUTERROR\",\"\\nXCOM.LOG\",\"\\nXCOMU3019E\",\"\\nYES\",\"\\nTRUNCATED\",\"\\nENCODING\",\"\\nUTF8\",\"\\nTRNENCRL\",\"\\nCIPHER\",\"\\nXCOMN3627I\",\"\\nLOAD\",\"\\nWRITING\",\"\\nCONFIGURATION\",\"\\nBUTTON\",\"\\nCNF\",\"\\nXML\",\"\\nXCOMU3643E\",\"\\nGLOBAL\",\"\\nCHARSET\",\"\\nCHARACTER\",\"\\nCONVERSION\",\"\\nRF\",\"\\nRECEIVE\",\"\\nIGNORED\",\"\\nDETECT\",\"\\nCACHE\",\"\\nREAD\",\"\\nSZ\",\"\\nMALFORMED\",\"\\nCODE\",\"\\nFLAG\",\"\\nXCOM.GLB\",\"\\nMBCS\",\"\\nMOVE\",\"\\nXCOMU0929E\",\"\\nLIST\",\"\\nREMOTE\",\"\\nOPERATOR\",\"\\nREMOVE\",\"\\nENCRYPT\",\"\\n+\",\"\\nINTERMEDIATE\",\"\\n!\",\"\\nNEGOTIATE\",\"\\nPING\",\"\\nAES\",\"\\nPRIOTIRY\",\"\\nUTF16\",\"\\nMEMBER\",\"\\nEDIT\",\"\\nSAVE\",\"\\nSYSTEM\",\"\\nNULL\",\"\\nDESTINATION\",\"\\nINDIRECT\",\"\\nAPPEND\",\"\\nMISPLACED\",\"\\nPOPULATED\",\"\\nXIDEST\",\"\\nBATCH\",\"\\nCALL\",\"\\nFAILED\",\"\\nCHECK\",\"\\nWARNING\",\"\\nXCOMPRE\",\"\\nLOCAL\",\"\\nLICENSE\",\"\\nSUPRESS\",\"\\nLICENSED\",\"\\nXCOMD\",\"\\nLONG\",\"\\nXCOMU0523E\",\"\\nXCOMU3670W\",\"\\nIMPORT\",\"\\nINSERT\",\"\\nEXTRACT\",\"\\nREST\",\"\\nGATEWAY\",\"\\nCOMMUNICATE\",\"\\nDELIVER\",\"\\nXCOM\",\"\\nPARAMTER\",\"\\nONWARD\",\"\\nWRITE\",\"\\nR11.6\",\"\\nXCOMU0526E\",\"\\nXCOMU0525E\",\"\\nTRUNCATION\",\"\\nPOLICY\",\"\\nFTP\",\"\\nGUID\",\"\\nMAXRECLEN\",\"\\nLENGTHS\",\"\\nDECRYPTED\",\"\\nXCOMU0438E\",\"\\nGATEWAYGUID\",\"\\nAES/ECB\",\"\\nPARAMETERS\",\"\\nHEADER\",\"\\nAPI\",\"\\nSERVER\",\"\\nADMIN\",\"\\nXCOMAPI\",\"\\nXLPCMD\",\"\\nXPPCMD\",\"\\nSHELL\",\"\\nCMD\",\"\\nXPRECMD\",\"\\nXENDCMD\",\"\\nXPULLCMD\",\"\\nXNOTIFYCMD\",\"\\n11.6\",\"\\nSOAP\",\"\\n929\",\"\\nTRUST\",\"\\nPASS\",\"\\nUSER\",\"\\nRUN\",\"\\nFIPS\",\"\\nMODE\",\"\\nDIR\",\"\\nTABLE\",\"\\nPFX\",\"\\nSECURITY\",\"\\nID\",\"\\nROOT\",\"\\nOWNER\",\"\\nSETTING\",\"\\nQUEUE\\u003dNO\",\"\\nXCOMU0286E\",\"\\nSPOHE01\",\"\\nNON-ROOT\",\"\\nS-BIT\",\"\\nPARAMETER\",\"\\nSPECIFIC\",\"\\nEXTRA\",\"\\nIN\",\"\\nINCLUDED\",\"\\nEATTR\",\"\\nEXIT\",\"\\nALLOCATION\",\"\\nFAULT\",\"\\nFAILS\",\"\\nPRE\",\"\\nXCOMU0322E\",\"\\nCA\",\"\\nPREALLOCATION\",\"\\n322\",\"\\nXCOMPRE_LOCAL\",\"\\nDATA\",\"\\nPROGRAM\",\"\\nSHELL_CMD\",\"\\nCACHE_WRITE_SZ\",\"\\nCACHE_READ_SZ\",\"\\nTRUST_ODBC\",\"\\nTRUST_PASS\",\"\\nTRUST_USER\",\"\\nTRUST_TABLE_PFX\",\"\\nFIPS_MODE\",\"\\nLICENSE_DIR\",\"\\nMESSAGE\",\"\\nTRNENCRL_CIPHER\",\"\\nTRNENCRR_CIPHER\",\"\\nCODE_FLAG\",\"\\nMBCS_INPUTERROR\",\"\\nREMOTE_CHARSET\",\"\\nDEFAULT_INPUTERROR\",\"\\nPROBLEM\",\"\\nOPENED\"","LICENSED":null,"COMPONENTNAME":"CA XCOM Data Transport for Linux PC","SOLUTIONNUMBER":"3","STATUS":"CONFIRMED","SOLUTIONDESCRIPTION":"<p><span>XCOMTCP crashes when the STARTDATE value is provided in an invalid<br></span><span>format instead of getting an appropriate error message.<br></span><span><br><br></span><span>SPECIAL INSTRUCTIONS:<br></span><span><br><br></span><span> After applying this solution, customers must:<br></span><span> - Recycle CA XCOM Data Transport Service<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>XCOMTCP crashes and a Segmentation fault will occur as shown below:<br></span><span><br><br></span><span> XCOMU0024I Transfer scheduled for future execution.<br></span><span> *** glibc detected *** xcomtcp: double free or corruption<br></span><span> (!prev): 0x09169958 ***<br></span><span> Segmentation fault.<br></span><span><br><br></span><span>IMPACT:<br></span><span> Users will fail to schedule the transfers for the specified time<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>The START_DATE parameter can be used to provide the date value or<br></span><span>ensure a valid date format is specified for the STARTDATE parameter<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 124<br></span><span><br><br></span><span>Specifying AVGREC=U for transfers results in history records not being<br></span><span>written to a DB2 database. This is due to an invalid value specified in the<br></span><span>VALUES clause of the INSERT statement for the AVGREC value.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The transfer history record is no longer displayed once it has been removed<br></span><span>from the queue.<br></span><span>SQLSTATE=22001 error message appears in the trace log for the transfer:<br></span><span><br><br></span><span> SQL0433N Value \"\" is too long.<br></span><span><br><br></span><span>IMPACT:<br></span><span>History records not written to DB2 when AVGREC=U is specified for a<br></span><span>transfer.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Modify the INSERT statement in the history.inserts file for this transfer.<br></span><span>In the VALUES clause, modify the value which is 19th from the end to be<br></span><span>\"x'80'\". Then use the history.inserts file to update the history database.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 125<br></span><span><br><br></span><span>Exporting history data from the CA XCOM Data Transport GUI to Easytrieve or<br></span><span>CSV format does not contain all the Unicode information as well as missing<br></span><span>zOS dataset extended attributes and record allocation information.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>- Full Unicode information for transfer requests are not shown in the<br></span><span> Easytrieve report or CSV file.<br></span><span>- Extended attributes for z/OS datasets are not recorded in the CSV file.<br></span><span>- z/OS datasets which were allocated based on records are reported as<br></span><span> allocated by track.<br></span><span><br><br></span><span>IMPACT:<br></span><span>Easytrieve reports and CSV files do not list all the Unicode information and<br></span><span>display the information for z/OS datasets as track allocated when they are<br></span><span>record allocated. In addition, the CSV file does not contain the extended<br></span><span>attribute information for z/OS datasets.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Run Easytrieve reports from a history file (histf) created from the<br></span><span>xcomtcp -c7 metatransfer.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 126<br></span><span><br><br></span><span>On starting the CA XCOM Data Transport GUI, a message<br></span><span><br><br></span><span> \"XCOMU3019E Error occurred on refreshing history records<br></span><span> java.lang.NullPointerException ExceptionMessage=null\"<br></span><span><br><br></span><span>is logged and can be viewed in the log browser.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>XCOMU3019E message appears in the XCOM log.<br></span><span><br><br></span><span>IMPACT:<br></span><span>There is no impact to the operation of the CA XCOM Data Transport GUI.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>None.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 127<br></span><span><br><br></span><span>A Unicode transfer, where the encoding parameter is set to UTF8 or UTF16,<br></span><span>can be submitted successfully through the GUI when the Truncate parameter is<br></span><span>set to YES. The transfer should fail since this is not valid with Unicode<br></span><span>transfers.<br></span><span><br><br></span><span>Symptoms:<br></span><span>The invalid transfer record gets submitted successfully and the following<br></span><span>message is displayed on the screen:<br></span><span> \"XCOMN3627I transfer scheduled successfully.\"<br></span><span><br><br></span><span>Impact:<br></span><span>The Unicode transfer will run instead of failing with an appropriate message<br></span><span>which can mislead users into thinking that their Unicode transfers were<br></span><span>successful.<br></span><span><br><br></span><span>Circumvention:<br></span><span>Ensure the Truncate parameter is set to No when submitting Unicode transfers<br></span><span>through the GUI.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 128<br></span><span><br><br></span><span>Attempting to load a CNF or XML file into the GUI fails and the file is not<br></span><span>loaded.<br></span><span><br><br></span><span>Symptoms:<br></span><span>The following error message is displayed trying to load a CNF or XML file<br></span><span>using the Load button in the GUI.<br></span><span><br><br></span><span> \"XCOMU3643E Problem writing into the Configuration file.\"<br></span><span><br><br></span><span>Impact:<br></span><span>The user cannot load and edit configuration files with the GUI.<br></span><span><br><br></span><span>Circumvention:<br></span><span>None.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 130<br></span><span><br><br></span><span>The local system ignores global parameter DEFAULT_INPUTERROR for a Unicode<br></span><span>receive file transfer when malformed characters are received from the remote<br></span><span>partner. This occurs when the remote file contains malformed characters and<br></span><span>the REMOTE_CHARSET is the same as CODE_FLAG (i.e., both are set to use the<br></span><span>UTF 8 character set or the UTF 16 character set).<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>A Unicode receive file transfer fails when the remote file contains<br></span><span>malformed characters and the REMOTE_CHARSET is the same as CODE_FLAG.<br></span><span><br><br></span><span>The transfer ends with error message:<br></span><span><br><br></span><span> XCOMU0929E Unicode conversion detected malformed characters. Transfer<br></span><span> terminated<br></span><span><br><br></span><span>The error occurs regardless of what is set for the local global parameter<br></span><span>DEFAULT_INPUTERROR.<br></span><span><br><br></span><span>IMPACT:<br></span><span>The Unicode receive file transfer fails even if DEFAULT_INPUTERROR is set<br></span><span>to SKIP, REPLACE, or REPLACE#n.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Specify the MBCS_INPUTERROR parameter on the receive file transfer and it<br></span><span>will be honored.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 131<br></span><span><br><br></span><span>Issuing the PING command where the operator ! has been specified for<br></span><span>the TRNENCRR_CIPHER and/or the TRNENCRL_CIPHER parameters, or the operator<br></span><span>+ has been specified for the TRNENCRR_CIPHER parameter, will cause the<br></span><span>cipher negotiation to return invalid results.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>An incorrect cipher is negotiated because the ! operator does not remove<br></span><span>the cipher from the list of ciphers and the + operator does not move the<br></span><span>cipher to the end of the list of ciphers.<br></span><span><br><br></span><span>IMPACT:<br></span><span>Encryption is not done with the appropriate cipher.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>No circumvention.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 133<br></span><span><br><br></span><span>A CNF configuration file that is loaded into the XCOM GUI that has specified<br></span><span>the XIDEST parameter set to a value of null will cause the transfer record<br></span><span>parameter values to be populated incorrectly when editing or saving the<br></span><span>configuration file.<br></span><span><br><br></span><span>Symptoms:<br></span><span>If the XIDEST parameter is set to null in the CNF file, then the remote<br></span><span>system value is misplaced and displayed as the Indirect Destination Member<br></span><span>parameter instead.<br></span><span><br><br></span><span>Impact:<br></span><span>The edited or saved transfer record may contain an invalid value and will<br></span><span>fail when submitted for scheduling.<br></span><span><br><br></span><span>Circumvention:<br></span><span>Check the parameter values for the edited record and correct the misplaced<br></span><span>values, if there are any.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 134<br></span><span><br><br></span><span>Suppress all CA License messages from the XCOM service, XCOM command line<br></span><span>and the XCOM GUI.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>CA License messages are issued by XCOM to either the screen or xcom.log<br></span><span>during XCOM processing.<br></span><span><br><br></span><span>IMPACT:<br></span><span>None. CA Licensing messages do not have an impact on XCOM functionality.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 135<br></span><span><br><br></span><span>XCOM R11.6 is not able to communicate with Gateway R11.6 and will fail when<br></span><span>trying to insert or extract files due to changes with the web services<br></span><span>technology in Gateway R11.6. As a result, XCOM R11.6 needs to be enhanced so<br></span><span>that its existing features \"Insert File to Gateway\" and \"Extract file from<br></span><span>Gateway\" will work with Gateway R11.6 as well as having new functionality<br></span><span>added so that it can do an \"Export from Gateway to an External Server\" and<br></span><span>an \"Import from an External Server to Gateway\".<br></span><span><br><br></span><span>Special Instructions:<br></span><span><br><br></span><span>After applying this solution, customers must:<br></span><span>- Add New Parameter \"GATEWAY_VERSION=R116\" to xcom.glb file manually or<br></span><span> set the value for GATEWAY VERSION from XCOM GUI Global Parameters section.<br></span><span>- Recycle CA XCOM Data Transport Service<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The XCOM R11.6 GA version is not able to communicate with Gateway R11.6 and<br></span><span>will return one of the following errors depending on the action being done.<br></span><span> \"XCOMU0525E CA XCOM Gateway file insertion failed:CA XCOM Gateway returned<br></span><span> an error\"<br></span><span> \"XCOMU0526E CA XCOM Gateway file extraction failed:CA XCOM Gateway returned<br></span><span> an error\"<br></span><span><br><br></span><span>IMPACT:<br></span><span>XCOM R11.6 will not be able to communicate with Gateway R11.6 to<br></span><span>insert/extract files or for onward delivery.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 136<br></span><span><br><br></span><span>Downloading a gateway file using either the XCOM GUI manually or the XCOM<br></span><span>onward delivery using a gateway encryption policy that specifies the AES/ECB<br></span><span>cipher results in the file remaining encrypted. This is observed when the<br></span><span>file is either uploaded/downloaded using FTP or the Gateway GUI and is then<br></span><span>downloaded/uploaded using XCOM.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span> - Downloaded file remains encrypted except for the first few characters.<br></span><span> - Onward delivery fails with the error \"XCOMU0438E Record length greater<br></span><span> than maxreclen, but truncation not allowed\".<br></span><span><br><br></span><span>IMPACT:<br></span><span>Users can't download a gateway file using the XCOM GUI manually or using the<br></span><span>XCOM onward delivery when the AES/ECB cipher is set in the gateway policy.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>A different cipher can be chosen in the gateway policy.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 137<br></span><span><br><br></span><span>The XCOMAPI contains some XCOM global parameters which would allow a<br></span><span>non-Administrator to change them.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>Any user can set a value for the global parameters that are listed below<br></span><span>from the XCOMAPI.<br></span><span><br><br></span><span>xlpcmd<br></span><span>xppcmd<br></span><span>xprecmd<br></span><span>xendcmd<br></span><span>xpullcmd<br></span><span>xpushcmd<br></span><span>xnotifycmd<br></span><span>shell_cmd<br></span><span>trust_odbc<br></span><span>trust_pass<br></span><span>trust_user<br></span><span>trust_table_pfx<br></span><span>cache_read_sz<br></span><span>mail_type<br></span><span>smtp_server<br></span><span>license_dir<br></span><span>fips_mode<br></span><span><br><br></span><span>IMPACT:<br></span><span>Non-Administrator users can override the XCOM global parameters set by<br></span><span>the administrator.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>NONE<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 138<br></span><span><br><br></span><span>In order to use the XCOM API with QUEUE=NO, the API program has to<br></span><span>have root ownership and the user s-bit set. This can be considered a<br></span><span>security exposure.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The following error will occur when the XCOM API is run without<br></span><span>these security settings:<br></span><span><br><br></span><span> XCOMU0286E Error setting local user id<br></span><span><br><br></span><span>IMPACT:<br></span><span>XCOM API transfers will fail when the expected security settings<br></span><span>are not used.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Run transfers in background, QUEUE=YES, and monitor for transfer<br></span><span>termination with \"xcomtcp -c6 ...\", possibly running this command<br></span><span>from the API with a system() call.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 140<br></span><span><br><br></span><span>The AVGREC and EATTR parameters should only be included in the XCOM header<br></span><span>when specified in the configuration file. However, these parameters are<br></span><span>always being added to the header even when they are not specified in the<br></span><span>configuration file.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The AVGREC and EATTR parameters are included in the XCOM header even if they<br></span><span>are not specified in the configuration file.<br></span><span><br><br></span><span>IMPACT:<br></span><span>When the AVGREC and EATTR parameters are not specified the configuration<br></span><span>file, the following values are sent to the partner:<br></span><span><br><br></span><span> AVGREC=NONE<br></span><span> EATTR=NO<br></span><span><br><br></span><span>This can cause unexpected results when sending a transfer to XCOM for z/OS<br></span><span>that will allocate a new file.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 141<br></span><span><br><br></span><span>When the global parameters XPRECMD=$XCOM_HOME/cmd/xcompre and<br></span><span>XCOMPRE_LOCAL=YES are set, a local transfer will terminate with a<br></span><span>segmentation fault instead of an error message if the preallocation<br></span><span>exit returns a non-zero return code.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>For a locally initiated transfer, the preallocation user exit runs prior to<br></span><span>connecting to the partner. When the preallocation user exit ends with a<br></span><span>non-zero return code, XCOM attempts to send the message to the partner even<br></span><span>though the connection doesn't yet exist. This causes a segmentation fault<br></span><span>and the XCOMU0322E message to be lost:<br></span><span><br><br></span><span> XCOMU0322E Preallocation User Exit failed, RC=nnn<br></span><span><br><br></span><span>IMPACT:<br></span><span>The segmentation fault prevents the XCOMU0322E message from being issued.<br></span><span>Without the XCOMU0322E message the user does not know why the transfer<br></span><span>failed.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>HYPER: NO<br></span><span><br><br></span><span>DISTRIBUTION CODE: A<br></span><span><br><br></span><span>PRODUCT(S) AFFECTED: CA XCOM Data Transport for Linux PC r11.6<br></span><span><br><br></span><span>DOWNLOAD INFORMATION:<br></span><span>---------------------<br></span><span>NODE: ftp.ca.com<br></span><span>PATH: /pub/xcom/xclx86/r11613014<br></span><span>FILES: XCLX86_XCOMPATCH_r11613014.bin<br></span><span> XCUNIX_r11613014_Patch_readme.htm<br></span></p>","TITLE":"XCOMTCP CRASHES WITH WRONG STARTDATE FORMAT","TYPE":null,"UPDATEDDATETIME":"2021-03-19T14:50:09.000Z","ACTION":"APPROVED","ASSIGNED":null,"PROBLEMPDT":["XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86","XCLX86"],"SMPFIXTP":"S","SMPFIXDATA2":null,"DEFTECH":null,"CNFTECH":null,"PROBLEMNO":["124"," 125"," 126"," 127"," 128"," 130"," 131"," 133"," 134"," 135"," 136"," 137"," 138"," 140"," 141"," 142"],"PROBLEMTITLE":["SQL0433N WRITING ODBC HISTORY WHEN AVGREC SPECIFIED","INCOMPLETE HISTF/CSV FILE CREATED ON EXPORT FROM GUI","XCOMU3019E ON STARTUP OF GUI","UNICODE GUI TRANSFER WITH TRUNCATE=YES DOES NOT FAIL","XCOMU3643E ERROR WHEN LOADING CNF/XML FILES INTO THE GUI","UNICODE: DEFAULT_INPUTERROR IGNORED FOR RECEIVE FILE","PING: WRONG CIPHER NEGOTIATED","MISPLACED PARAMETER VALUES WHEN EDITING CNF FILES IN GUI","LICENSE - SUPPRESS CA LICENSE MESSAGES","GATEWAY BRIDGE SUPPORT FOR GATEWAY R11.6","GATEWAY FILE NOT DECRYPTED CORRECTLY","REMOVE XCOM GLOBAL PARAMETERS FROM XCOMAPI","API - RUN XCOM QUEUE=NO AS NON-ROOT","TRANSFER - AVGREC AND EATTR ALWAYS IN XCOM HEADER","XCOMPRE - LOCAL PREALLOCATION EXIT ERROR SEGMENTATION FAULT","XCOMTCP CRASHES WITH WRONG STARTDATE FORMAT"],"RELEASE":"11.6","SMPFIXDATA":"T53S954","SUPPORT_PRODUCT_ID":null,"SOURCE":"UI","UPDATED_BY":null,"CREATED_BY":null,"SOURCEID":null,"INTERNALCOMMENT":null,"SUPPORT_PRODUCT":null,"apar_metadata_id":739514,"solution_apar_num":"RO58255","solution_os":"LINUX","ftp_url_addr":"/apars/d15/pXCLX86/r11.6/oLINUX/RO58255.txt","solution_apar_status_cd":"C ","file_size":24272,"creation_time":null,"last_updated_time":null,"last_updated_by":null,"PRBTITLE":"SQL0433N WRITING ODBC HISTORY WHEN AVGREC SPECIFIED%INCOMPLETE HISTF/CSV FILE CREATED ON EXPORT FROM GUI%XCOMU3019E ON STARTUP OF GUI%UNICODE GUI TRANSFER WITH TRUNCATE=YES DOES NOT FAIL%XCOMU3643E ERROR WHEN LOADING CNF/XML FILES INTO THE GUI%UNICODE: DEFAULT_INPUTERROR IGNORED FOR RECEIVE FILE%PING: WRONG CIPHER NEGOTIATED%MISPLACED PARAMETER VALUES WHEN EDITING CNF FILES IN GUI%LICENSE - SUPPRESS CA LICENSE MESSAGES%GATEWAY BRIDGE SUPPORT FOR GATEWAY R11.6%GATEWAY FILE NOT DECRYPTED CORRECTLY%REMOVE XCOM GLOBAL PARAMETERS FROM XCOMAPI%API - RUN XCOM QUEUE=NO AS NON-ROOT%TRANSFER - AVGREC AND EATTR ALWAYS IN XCOM HEADER%XCOMPRE - LOCAL PREALLOCATION EXIT ERROR SEGMENTATION FAULT%XCOMTCP CRASHES WITH WRONG STARTDATE FORMAT","solutionDownloads":[{"filePath":"/apars/d15/pXCLX86/r11.6/oLINUX/RO58255.txt","fileSize":"24272","fileName":"RO58255.txt"},{"filePath":"/CAproducts/xcom/xclx86/r11613014/XCLX86_XCOMPATCH_r11613014.bin","fileSize":"71654734","fileName":"XCLX86_XCOMPATCH_r11613014.bin"},{"filePath":"/CAproducts/xcom/xclx86/r11613014/XCUNIX_r11613014_Patch_readme.htm","fileSize":"60156","fileName":"XCUNIX_r11613014_Patch_readme.htm"}],"relatedProblems":[{"number":"124","product":"XCLX86","title":"SQL0433N WRITING ODBC HISTORY WHEN AVGREC SPECIFIED"},{"number":"125","product":"XCLX86","title":"INCOMPLETE HISTF/CSV FILE CREATED ON EXPORT FROM GUI"},{"number":"126","product":"XCLX86","title":"XCOMU3019E ON STARTUP OF GUI"},{"number":"127","product":"XCLX86","title":"UNICODE GUI TRANSFER WITH TRUNCATE=YES DOES NOT FAIL"},{"number":"128","product":"XCLX86","title":"XCOMU3643E ERROR WHEN LOADING CNF/XML FILES INTO THE GUI"},{"number":"130","product":"XCLX86","title":"UNICODE: DEFAULT_INPUTERROR IGNORED FOR RECEIVE FILE"},{"number":"131","product":"XCLX86","title":"PING: WRONG CIPHER NEGOTIATED"},{"number":"133","product":"XCLX86","title":"MISPLACED PARAMETER VALUES WHEN EDITING CNF FILES IN GUI"},{"number":"134","product":"XCLX86","title":"LICENSE - SUPPRESS CA LICENSE MESSAGES"},{"number":"135","product":"XCLX86","title":"GATEWAY BRIDGE SUPPORT FOR GATEWAY R11.6"},{"number":"136","product":"XCLX86","title":"GATEWAY FILE NOT DECRYPTED CORRECTLY"},{"number":"137","product":"XCLX86","title":"REMOVE XCOM GLOBAL PARAMETERS FROM XCOMAPI"},{"number":"138","product":"XCLX86","title":"API - RUN XCOM QUEUE=NO AS NON-ROOT"},{"number":"140","product":"XCLX86","title":"TRANSFER - AVGREC AND EATTR ALWAYS IN XCOM HEADER"},{"number":"141","product":"XCLX86","title":"XCOMPRE - LOCAL PREALLOCATION EXIT ERROR SEGMENTATION FAULT"},{"number":"142","product":"XCLX86","title":"XCOMTCP CRASHES WITH WRONG STARTDATE FORMAT"}],"dependencies":[{"data":"T53S954","type":"SUPERSEDES"}],"sourceIdDetails":[],"confirmedDate":"5/1/2013","updatedDate":"3/19/2021","createdDate":"5/1/2013","hyperFlag":"false","componentName":"CA XCOM Data Transport for Linux PC","componentCode":"XCLX86","solutionNumber":"3","release":"11.6","DistributionCode":"AVAILABLE","os":"LINUX","solutionTitle":"XCOMTCP CRASHES WITH WRONG STARTDATE FORMAT","text":"<p><span>XCOMTCP crashes when the STARTDATE value is provided in an invalid<br></span><span>format instead of getting an appropriate error message.<br></span><span><br><br></span><span>SPECIAL INSTRUCTIONS:<br></span><span><br><br></span><span> After applying this solution, customers must:<br></span><span> - Recycle CA XCOM Data Transport Service<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>XCOMTCP crashes and a Segmentation fault will occur as shown below:<br></span><span><br><br></span><span> XCOMU0024I Transfer scheduled for future execution.<br></span><span> *** glibc detected *** xcomtcp: double free or corruption<br></span><span> (!prev): 0x09169958 ***<br></span><span> Segmentation fault.<br></span><span><br><br></span><span>IMPACT:<br></span><span> Users will fail to schedule the transfers for the specified time<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>The START_DATE parameter can be used to provide the date value or<br></span><span>ensure a valid date format is specified for the STARTDATE parameter<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 124<br></span><span><br><br></span><span>Specifying AVGREC=U for transfers results in history records not being<br></span><span>written to a DB2 database. This is due to an invalid value specified in the<br></span><span>VALUES clause of the INSERT statement for the AVGREC value.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The transfer history record is no longer displayed once it has been removed<br></span><span>from the queue.<br></span><span>SQLSTATE=22001 error message appears in the trace log for the transfer:<br></span><span><br><br></span><span> SQL0433N Value \"\" is too long.<br></span><span><br><br></span><span>IMPACT:<br></span><span>History records not written to DB2 when AVGREC=U is specified for a<br></span><span>transfer.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Modify the INSERT statement in the history.inserts file for this transfer.<br></span><span>In the VALUES clause, modify the value which is 19th from the end to be<br></span><span>\"x'80'\". Then use the history.inserts file to update the history database.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 125<br></span><span><br><br></span><span>Exporting history data from the CA XCOM Data Transport GUI to Easytrieve or<br></span><span>CSV format does not contain all the Unicode information as well as missing<br></span><span>zOS dataset extended attributes and record allocation information.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>- Full Unicode information for transfer requests are not shown in the<br></span><span> Easytrieve report or CSV file.<br></span><span>- Extended attributes for z/OS datasets are not recorded in the CSV file.<br></span><span>- z/OS datasets which were allocated based on records are reported as<br></span><span> allocated by track.<br></span><span><br><br></span><span>IMPACT:<br></span><span>Easytrieve reports and CSV files do not list all the Unicode information and<br></span><span>display the information for z/OS datasets as track allocated when they are<br></span><span>record allocated. In addition, the CSV file does not contain the extended<br></span><span>attribute information for z/OS datasets.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Run Easytrieve reports from a history file (histf) created from the<br></span><span>xcomtcp -c7 metatransfer.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 126<br></span><span><br><br></span><span>On starting the CA XCOM Data Transport GUI, a message<br></span><span><br><br></span><span> \"XCOMU3019E Error occurred on refreshing history records<br></span><span> java.lang.NullPointerException ExceptionMessage=null\"<br></span><span><br><br></span><span>is logged and can be viewed in the log browser.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>XCOMU3019E message appears in the XCOM log.<br></span><span><br><br></span><span>IMPACT:<br></span><span>There is no impact to the operation of the CA XCOM Data Transport GUI.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>None.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 127<br></span><span><br><br></span><span>A Unicode transfer, where the encoding parameter is set to UTF8 or UTF16,<br></span><span>can be submitted successfully through the GUI when the Truncate parameter is<br></span><span>set to YES. The transfer should fail since this is not valid with Unicode<br></span><span>transfers.<br></span><span><br><br></span><span>Symptoms:<br></span><span>The invalid transfer record gets submitted successfully and the following<br></span><span>message is displayed on the screen:<br></span><span> \"XCOMN3627I transfer scheduled successfully.\"<br></span><span><br><br></span><span>Impact:<br></span><span>The Unicode transfer will run instead of failing with an appropriate message<br></span><span>which can mislead users into thinking that their Unicode transfers were<br></span><span>successful.<br></span><span><br><br></span><span>Circumvention:<br></span><span>Ensure the Truncate parameter is set to No when submitting Unicode transfers<br></span><span>through the GUI.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 128<br></span><span><br><br></span><span>Attempting to load a CNF or XML file into the GUI fails and the file is not<br></span><span>loaded.<br></span><span><br><br></span><span>Symptoms:<br></span><span>The following error message is displayed trying to load a CNF or XML file<br></span><span>using the Load button in the GUI.<br></span><span><br><br></span><span> \"XCOMU3643E Problem writing into the Configuration file.\"<br></span><span><br><br></span><span>Impact:<br></span><span>The user cannot load and edit configuration files with the GUI.<br></span><span><br><br></span><span>Circumvention:<br></span><span>None.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 130<br></span><span><br><br></span><span>The local system ignores global parameter DEFAULT_INPUTERROR for a Unicode<br></span><span>receive file transfer when malformed characters are received from the remote<br></span><span>partner. This occurs when the remote file contains malformed characters and<br></span><span>the REMOTE_CHARSET is the same as CODE_FLAG (i.e., both are set to use the<br></span><span>UTF 8 character set or the UTF 16 character set).<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>A Unicode receive file transfer fails when the remote file contains<br></span><span>malformed characters and the REMOTE_CHARSET is the same as CODE_FLAG.<br></span><span><br><br></span><span>The transfer ends with error message:<br></span><span><br><br></span><span> XCOMU0929E Unicode conversion detected malformed characters. Transfer<br></span><span> terminated<br></span><span><br><br></span><span>The error occurs regardless of what is set for the local global parameter<br></span><span>DEFAULT_INPUTERROR.<br></span><span><br><br></span><span>IMPACT:<br></span><span>The Unicode receive file transfer fails even if DEFAULT_INPUTERROR is set<br></span><span>to SKIP, REPLACE, or REPLACE#n.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Specify the MBCS_INPUTERROR parameter on the receive file transfer and it<br></span><span>will be honored.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 131<br></span><span><br><br></span><span>Issuing the PING command where the operator ! has been specified for<br></span><span>the TRNENCRR_CIPHER and/or the TRNENCRL_CIPHER parameters, or the operator<br></span><span>+ has been specified for the TRNENCRR_CIPHER parameter, will cause the<br></span><span>cipher negotiation to return invalid results.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>An incorrect cipher is negotiated because the ! operator does not remove<br></span><span>the cipher from the list of ciphers and the + operator does not move the<br></span><span>cipher to the end of the list of ciphers.<br></span><span><br><br></span><span>IMPACT:<br></span><span>Encryption is not done with the appropriate cipher.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>No circumvention.<br></span><span><br><br></span><span>Problem Description:<br></span><span>XCLX86 133<br></span><span><br><br></span><span>A CNF configuration file that is loaded into the XCOM GUI that has specified<br></span><span>the XIDEST parameter set to a value of null will cause the transfer record<br></span><span>parameter values to be populated incorrectly when editing or saving the<br></span><span>configuration file.<br></span><span><br><br></span><span>Symptoms:<br></span><span>If the XIDEST parameter is set to null in the CNF file, then the remote<br></span><span>system value is misplaced and displayed as the Indirect Destination Member<br></span><span>parameter instead.<br></span><span><br><br></span><span>Impact:<br></span><span>The edited or saved transfer record may contain an invalid value and will<br></span><span>fail when submitted for scheduling.<br></span><span><br><br></span><span>Circumvention:<br></span><span>Check the parameter values for the edited record and correct the misplaced<br></span><span>values, if there are any.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 134<br></span><span><br><br></span><span>Suppress all CA License messages from the XCOM service, XCOM command line<br></span><span>and the XCOM GUI.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>CA License messages are issued by XCOM to either the screen or xcom.log<br></span><span>during XCOM processing.<br></span><span><br><br></span><span>IMPACT:<br></span><span>None. CA Licensing messages do not have an impact on XCOM functionality.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 135<br></span><span><br><br></span><span>XCOM R11.6 is not able to communicate with Gateway R11.6 and will fail when<br></span><span>trying to insert or extract files due to changes with the web services<br></span><span>technology in Gateway R11.6. As a result, XCOM R11.6 needs to be enhanced so<br></span><span>that its existing features \"Insert File to Gateway\" and \"Extract file from<br></span><span>Gateway\" will work with Gateway R11.6 as well as having new functionality<br></span><span>added so that it can do an \"Export from Gateway to an External Server\" and<br></span><span>an \"Import from an External Server to Gateway\".<br></span><span><br><br></span><span>Special Instructions:<br></span><span><br><br></span><span>After applying this solution, customers must:<br></span><span>- Add New Parameter \"GATEWAY_VERSION=R116\" to xcom.glb file manually or<br></span><span> set the value for GATEWAY VERSION from XCOM GUI Global Parameters section.<br></span><span>- Recycle CA XCOM Data Transport Service<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The XCOM R11.6 GA version is not able to communicate with Gateway R11.6 and<br></span><span>will return one of the following errors depending on the action being done.<br></span><span> \"XCOMU0525E CA XCOM Gateway file insertion failed:CA XCOM Gateway returned<br></span><span> an error\"<br></span><span> \"XCOMU0526E CA XCOM Gateway file extraction failed:CA XCOM Gateway returned<br></span><span> an error\"<br></span><span><br><br></span><span>IMPACT:<br></span><span>XCOM R11.6 will not be able to communicate with Gateway R11.6 to<br></span><span>insert/extract files or for onward delivery.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 136<br></span><span><br><br></span><span>Downloading a gateway file using either the XCOM GUI manually or the XCOM<br></span><span>onward delivery using a gateway encryption policy that specifies the AES/ECB<br></span><span>cipher results in the file remaining encrypted. This is observed when the<br></span><span>file is either uploaded/downloaded using FTP or the Gateway GUI and is then<br></span><span>downloaded/uploaded using XCOM.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span> - Downloaded file remains encrypted except for the first few characters.<br></span><span> - Onward delivery fails with the error \"XCOMU0438E Record length greater<br></span><span> than maxreclen, but truncation not allowed\".<br></span><span><br><br></span><span>IMPACT:<br></span><span>Users can't download a gateway file using the XCOM GUI manually or using the<br></span><span>XCOM onward delivery when the AES/ECB cipher is set in the gateway policy.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>A different cipher can be chosen in the gateway policy.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 137<br></span><span><br><br></span><span>The XCOMAPI contains some XCOM global parameters which would allow a<br></span><span>non-Administrator to change them.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>Any user can set a value for the global parameters that are listed below<br></span><span>from the XCOMAPI.<br></span><span><br><br></span><span>xlpcmd<br></span><span>xppcmd<br></span><span>xprecmd<br></span><span>xendcmd<br></span><span>xpullcmd<br></span><span>xpushcmd<br></span><span>xnotifycmd<br></span><span>shell_cmd<br></span><span>trust_odbc<br></span><span>trust_pass<br></span><span>trust_user<br></span><span>trust_table_pfx<br></span><span>cache_read_sz<br></span><span>mail_type<br></span><span>smtp_server<br></span><span>license_dir<br></span><span>fips_mode<br></span><span><br><br></span><span>IMPACT:<br></span><span>Non-Administrator users can override the XCOM global parameters set by<br></span><span>the administrator.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>NONE<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 138<br></span><span><br><br></span><span>In order to use the XCOM API with QUEUE=NO, the API program has to<br></span><span>have root ownership and the user s-bit set. This can be considered a<br></span><span>security exposure.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The following error will occur when the XCOM API is run without<br></span><span>these security settings:<br></span><span><br><br></span><span> XCOMU0286E Error setting local user id<br></span><span><br><br></span><span>IMPACT:<br></span><span>XCOM API transfers will fail when the expected security settings<br></span><span>are not used.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>Run transfers in background, QUEUE=YES, and monitor for transfer<br></span><span>termination with \"xcomtcp -c6 ...\", possibly running this command<br></span><span>from the API with a system() call.<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 140<br></span><span><br><br></span><span>The AVGREC and EATTR parameters should only be included in the XCOM header<br></span><span>when specified in the configuration file. However, these parameters are<br></span><span>always being added to the header even when they are not specified in the<br></span><span>configuration file.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>The AVGREC and EATTR parameters are included in the XCOM header even if they<br></span><span>are not specified in the configuration file.<br></span><span><br><br></span><span>IMPACT:<br></span><span>When the AVGREC and EATTR parameters are not specified the configuration<br></span><span>file, the following values are sent to the partner:<br></span><span><br><br></span><span> AVGREC=NONE<br></span><span> EATTR=NO<br></span><span><br><br></span><span>This can cause unexpected results when sending a transfer to XCOM for z/OS<br></span><span>that will allocate a new file.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>PROBLEM DESCRIPTION:<br></span><span>XCLX86 141<br></span><span><br><br></span><span>When the global parameters XPRECMD=$XCOM_HOME/cmd/xcompre and<br></span><span>XCOMPRE_LOCAL=YES are set, a local transfer will terminate with a<br></span><span>segmentation fault instead of an error message if the preallocation<br></span><span>exit returns a non-zero return code.<br></span><span><br><br></span><span>SYMPTOMS:<br></span><span>For a locally initiated transfer, the preallocation user exit runs prior to<br></span><span>connecting to the partner. When the preallocation user exit ends with a<br></span><span>non-zero return code, XCOM attempts to send the message to the partner even<br></span><span>though the connection doesn't yet exist. This causes a segmentation fault<br></span><span>and the XCOMU0322E message to be lost:<br></span><span><br><br></span><span> XCOMU0322E Preallocation User Exit failed, RC=nnn<br></span><span><br><br></span><span>IMPACT:<br></span><span>The segmentation fault prevents the XCOMU0322E message from being issued.<br></span><span>Without the XCOMU0322E message the user does not know why the transfer<br></span><span>failed.<br></span><span><br><br></span><span>CIRCUMVENTION:<br></span><span>N/A<br></span><span><br><br></span><span>HYPER: NO<br></span><span><br><br></span><span>DISTRIBUTION CODE: A<br></span><span><br><br></span><span>PRODUCT(S) AFFECTED: CA XCOM Data Transport for Linux PC r11.6<br></span><span><br><br></span><span>DOWNLOAD INFORMATION:<br></span><span>---------------------<br></span><span>NODE: ftp.ca.com<br></span><span>PATH: /pub/xcom/xclx86/r11613014<br></span><span>FILES: XCLX86_XCOMPATCH_r11613014.bin<br></span><span> XCUNIX_r11613014_Patch_readme.htm<br></span></p>","keywordDetails":["COMMAND","INVALID","ERROR","LINE","SEGMENTATION","FORMAT","DATE","TRANSFER","CRASH","START","PRODUCT","SIGSEGV","COMMANDLINE","STARTDATE","XCOMTCP","START_DATE","WRONG FORMAT","RO58255","T53S954","WRONG","HISTORY","RECORD","DATABASE","VALUE","NOT","DB2","LARGE","STANDALONEUI","WRITTEN","TOO","AVGREC","ODBC","SQLSTATE","22001","MYSQL","SQL0433N","EXTENDED","REPORT","FILE","EXPORT","ATTRIBUTE","INCOMPLETE","INFORMATION","MISSING","EASYTRIEVE","CSV","GUI","UNICODE","HISTF","LOG","STARTUP","BROWSER","DEFAULT","INPUTERROR","XCOM.LOG","XCOMU3019E","YES","TRUNCATED","ENCODING","UTF8","TRNENCRL","CIPHER","XCOMN3627I","LOAD","WRITING","CONFIGURATION","BUTTON","CNF","XML","XCOMU3643E","GLOBAL","CHARSET","CHARACTER","CONVERSION","RF","RECEIVE","IGNORED","DETECT","CACHE","READ","SZ","MALFORMED","CODE","FLAG","XCOM.GLB","MBCS","MOVE","XCOMU0929E","LIST","REMOTE","OPERATOR","REMOVE","ENCRYPT","+","INTERMEDIATE","!","NEGOTIATE","PING","AES","PRIOTIRY","UTF16","MEMBER","EDIT","SAVE","SYSTEM","NULL","DESTINATION","INDIRECT","APPEND","MISPLACED","POPULATED","XIDEST","BATCH","CALL","FAILED","CHECK","WARNING","XCOMPRE","LOCAL","LICENSE","SUPRESS","LICENSED","XCOMD","LONG","XCOMU0523E","XCOMU3670W","IMPORT","INSERT","EXTRACT","REST","GATEWAY","COMMUNICATE","DELIVER","XCOM","PARAMTER","ONWARD","WRITE","R11.6","XCOMU0526E","XCOMU0525E","TRUNCATION","POLICY","FTP","GUID","MAXRECLEN","LENGTHS","DECRYPTED","XCOMU0438E","GATEWAYGUID","AES/ECB","PARAMETERS","HEADER","API","SERVER","ADMIN","XCOMAPI","XLPCMD","XPPCMD","SHELL","CMD","XPRECMD","XENDCMD","XPULLCMD","XNOTIFYCMD","11.6","SOAP","929","TRUST","PASS","USER","RUN","FIPS","MODE","DIR","TABLE","PFX","SECURITY","ID","ROOT","OWNER","SETTING","QUEUEu003dNO","XCOMU0286E","SPOHE01","NON-ROOT","S-BIT","PARAMETER","SPECIFIC","EXTRA","IN","INCLUDED","EATTR","EXIT","ALLOCATION","FAULT","FAILS","PRE","XCOMU0322E","CA","PREALLOCATION","322","XCOMPRE_LOCAL","DATA","PROGRAM","SHELL_CMD","CACHE_WRITE_SZ","CACHE_READ_SZ","TRUST_ODBC","TRUST_PASS","TRUST_USER","TRUST_TABLE_PFX","FIPS_MODE","LICENSE_DIR","MESSAGE","TRNENCRL_CIPHER","TRNENCRR_CIPHER","CODE_FLAG","MBCS_INPUTERROR","REMOTE_CHARSET","DEFAULT_INPUTERROR","PROBLEM","OPENED"],"authorized":true}}}]
{{addAlltoCartErrorMsgExceed}}.
| File name |
File Size |
Add to Cart |
Download |
| {{eachSolutionDownload.fileName}} |
{{bytesToSize(eachSolutionDownload.fileSize)}} |
Remove From Cart
Add To Cart
|
HTTP Via Browser
FTP
|
| Solution Number |
Fix Type |
| {{solutionDependency.data}} |
{{solutionDependency.type}} |
{{errorMsg}}
No solution details found