************************************************************************ * The following information provides more detail about the APARs fixed * * by this CSD (XR20465). * * * * CURRENT MAINTENANCE SYSLEVEL SERVICED IS: XR00007 * * * * * * Netview Distribution Manager/2 Version 2.0 * * * ************************************************************************ PTRNBR: 2M04018 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: PROBLEM WHEN DOS CLIENT AND CC SERVER HAVE THE SAME NAME PROBLEM SUMMARY : Define a DOS client with the same Name of a CC Server. The DOS client successfully starts, but when a CM request is received it loops logging the message: The name 'Client Name' is already in use in the Network. COMPONENTS CHANGED OR ENHANCED: ANXCMLDR.COM PROBLEM CONCLUSION: The defect has been solved adding a stronger check on the NETBIOS names defined in the network at the CMLOADER's startup. PTRNBR: 2M04041 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: CID: MESSAGE 1311 SHOULD BE LESS RUDE PROBLEM SUMMARY : message 1311 should say: 'the rc is not recognized by NetView DM/2' and not 'the rc is not an architectured rc for CID'. COMPONENTS CHANGED OR ENHANCED: ANX.MSG ANXH.MSG PROBLEM CONCLUSION: Message and its help changed such as: ANX1311: (E) This Exit Code is not recognized from NetView DM/2. EXPLANATION: The invoked program failed returning an exit code that is not recognized to be standard for CID products. SYSTEM ACTION: Processing continues and the request is considered as unsuccessful. USER RESPONSE: Check the product publication for the external program that failed about the specific exit code. Further information could be found in the External Program Log File if any was produced. PTRNBR: 2M04104 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: RECORDS LOST DURING TXT COMPRESSED FIXED FILE PROBLEM SUMMARY : Assume the following scenario: SEND from HOST to NvDM/2 node of a resource with the following characteristics: * The resource is sent compressed with NVDMLZW algorithm * The resource is a text file with fixed record length * The resource decompressed at node is small than 64K bytes but it is very close to 64K bytes. * The resource translated in ASCII at node is more than 64K bytes. . In the above conditions,during the node transform operation some bytes are lost. The SEND operation terminates with OK return code. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: When a fixed record length file is translated by node, the translated file size is larger than the origin one. If a file is close to 64K bytes (one buffer), when it is translated, the Transform Handler component needs two buffers to put more of 64K translated bytes. The problem is due to wrong EOF handling. In fact, when the buffer with about 64K bytes to translate is the last or the only buffer,a wrong test on EOF terminates the translation process. The bytes that aren't put into the buffer, results as lost. File handling corrected. PTRNBR: 2M04115 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: BAD PERFOMRNACE INSTALLING ON DOS CLIENT PROBLEM SUMMARY : Installing on a Dos WS,if the files are to be replaced (Already existing) on the Target Directory the performance are worst then if the file must be created. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: The problem was due to the creation of temporary files during the unpack. PTRNBR: 2M04126 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: PMR4656X, ACTIVATE WITH DEVICE A: DISABLED AT BOOT TIME PROBLEM SUMMARY : This problem has been opened to give a quick solution to the Customer POSTGIRO (PMR 4656X,B180,C846). The purpose is to allow the ACTIVATE also in case there is a diskette inserted in drive A: or B: . This to support the case for which the drive A: has been disabled, via hardware, at boot time. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The solution consist of setting an environment variable by adding in the config.sys the statement: SET ANXCHECKBOOT=NO This allow the End User to prevent check on the drives A: and B: before to activate the workstation. PTRNBR: 2M04128 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: ANX0203 MESSAGE WHEN INSTALLING TABLE MORE THAN 8 CHARS PROBLEM SUMMARY : When installing a Database Table with a name longer than 8 characters, NetView DM/2 issues message ANX0203 and ends unsuccessfully. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Now the End User can specify up to 16 characters. PTRNBR: 2M04135 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: CHANGE CONTROLLER WENT DOWN PROBLEM SUMMARY : The Change Controller went and the following logs where retrieved from both MESSAGE and ERROR log files: On message dat: ANX0082 SNA/FS Server detected an error (this occurred just after the deletion of SYST.SOFTW.160.REF.01) On ERROR DAT: a) Error generated in module A09CPPIT b) Error generated in module TCKERNEL c) Error generated in module ANXACPSU Return Code Primary = 20 Secondary = 0 Auxiliary = 8 d) Error generated in module ANXCSCNS COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The meaningful error is the following: . ** NetView DM/2 logged at 11:12:13 (PM) 06-03-1994 ** Error detected in NetView DM/2 DS component. The error was generated in module A09CPPIT. Additional Data : 41 30 39 43 50 50 49 54 30 30 30 34 34 00 00 08 A09CPPIT00044... 41 4e 58 43 53 30 4d 42 00 00 00 00 00 00 00 00 ANXCS0MB........ 20 20 20 20 20 20 20 20 08 00 14 00 08 00 00 00 ........ 00 00 00 00 00 00 54 01 01 00 00 00 00 00 00 00 ......T......... . The problem was due to the Specific Server that did not release memory. PTRNBR: 2M04143 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: INCORRECT SCB COMPRESSION OF A TXT FILE PROBLEM SUMMARY : Assume to SEND from NvDM/2 node a TXT file of 1546182 bytes of size. The file is compressed during the send operation with SCB algorithm. The SEND operation ended with OK return code but the SCB algorithm didn't work correctly because adds two characters in the middle of the compressed file. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem occurs in a particular compress condition: 1) INPUT DATA RECORD to compress is terminated. 2) OUTPUT COMPRESSED RECORD is full. 3) The last two bytes in the INPUT record are equal. With these three conditions the Specific Server wrongs to calculate the number of written bytes in the next OUTPUT COMPRESSED RECORD (more two bytes). PTRNBR: 2M04145 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: EMPTY SUBDIR DELETED AFTER REMOVE IN SERVICE+ACTIVATE PROBLEM SUMMARY : After a Remove in service area and an Activate all the empty directories under the path were the package was installed are deleted. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXACTVF.EXE ANXACTVF.SYS ANXACTVF.DLL ANXCMSRV.EXE ANX.MSG PROBLEM CONCLUSION: The problem was due to a not correct management for empty directories after a remove in service and the activate. Now, only the empty directories that belong to the package to be removed are deleted. PTRNBR: 2M04150 APARNBR: PJ16757 PTFNBR: XR20465 EXTERNAL SYMPTOM: PMR 2X908, IN A LARGE WAN NETWORK,SOMETIMES CLIENTS ARE NOT CONTACTED FROM THE SERVER. PROBLEM SUMMARY : In a large WAN network with about 80 clients connected to the Server via multiple bridges (local and remote),it happened that sometimes many clients are not contacted from the server when a request is submitted to them. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE ANXCSCNS.DLL ANXCSCNN.DLL ANXCSCNP.DLL PROBLEM CONCLUSION: A Sniffer Trace reveled that at Start Up time the Server was not able to connect all the clients that were waiting for it. The Startup and Signaling logic of both Server and Client were redesigned in order to avoid the useless connection and to avoid the possibility of waking up all clients simultaneously to let these connect. The solution has enhanced the signaling strength and reduced the network traffic at StartUp time. PTRNBR: 2M04153 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: FILES NOT MOVED BY ACTIVATE DUE TO EMPTY ACTIVATION LIST FILE PROBLEM SUMMARY : If an install on service (or a remove on service) is performed and before the activate is issued the machine is powered off, when the system restarts the IBMNVDM2.ALS file is empty notwithstanding the CHKDSK has been started. The result is that when the activate is issued the files in the Service area are not moved in the Active area because of the missed info. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The problem is due to the fact that the IBMNVDM2.ALS is kept always opened while the CDM agent is active. When the system restarts the CHKDSK encounter an allocation problem for the file IBMNVDM2.ALS but the file is not restored. Now the problem is solved by changing the open close of this file. PTRNBR: 2M04154 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: ACTIVATE DOES NOT CREATE SOME DIRECTORIES IN ACTIVE AREA PROBLEM SUMMARY : If the package to be installed has a directory structure for which some directories have a name included in another name,for example: D:«DB D:«DBUPDATE The install on Service Area is ok but the Activate fails because the shorter dir is not created and the files contained in it are not moved. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The problem is due to the way to check the directories names. This condition is now correctly managed. PTRNBR: 2M04157 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: ACTIVATE FAILS AFTER REMOVE OF A PACKAGE IN IRA STATUS PROBLEM SUMMARY : Issuing an Install on service removable, then a Remove of the same package, when the Activate is issued it ends in error after the reboot. The problem is that the Install on service adds the commands in the Activation List, but the remove does not delete these command. It remove only the files in the Service Area, so, when the Activate is issued it fails because the files related to the activation list are not found. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: The problem, now fixed, was due to incorrect management of the Activation List. PTRNBR: 2M04161 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: INITIATE DOESN'T WORK WITH DBCS CODEPAGES. PROBLEM SUMMARY : Since the conversion routine for INITIATE parms has been changed in order to call the GET_CP_CONVERT_TABLE API of the Comm.Mgr. The problem arises when the Target code page of the conversion (i.e.: the code page of the machine target of the INITIATE) is not supported by this API, as for DBCS code pages. In this situation the Comm. Mgr. returns an error to the Change Controller which ends because of errors. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: When a DBCS code page is found (i.e. 932,942,934,944,938,948 or 949) the conversion is made into a SBCS code page: the first one prepared for that machine or, by default, 850. PTRNBR: 2M04163 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: DOS PRISTINE HAS TO GO ON EVEN IF IBM NETBIOS NOT FOUND PROBLEM SUMMARY : The DOS client installation checks config.sys for IBM NetBIOS in case the target installation boot drive is different than the actual one. In case no DXM* files are found the installation is stopped exiting with the error NETBIOS NOT FOUND. On the contrary only a warning should be done not to prevent the use of other kinds of NetBIOS protocol. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE ANXIDNST.MSG PROBLEM CONCLUSION: Now, in case no DXM* file is found a new message is shown: ANX7280(W) IBM Netbios results not installed querying installation boot drive. Please be sure that a supported NetBIOS is actually installed. The installation is completed normally and return FE00 . At the same time the statement in startup.bat are located after PATH, NETBEUI and NETBIND statements if they are found. PTRNBR: 2M04165 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: CC ENDED BECAUSE OF ERRORS DURING HOST SEND WITH REPLACE OPERATION PROBLEM SUMMARY : Assume to submit a SEND from HOST to NvDM/2 specifying destruction allowed and having the global name to be stored different than that to be deleted. At NvDM/2 node the global name to store is not cataloged while that to delete is in INRU status. The above task ends with both SNA/FS Server and Change Controller errors logged at NvDM/2. At the HOST site, the task is reported ended with RC=8 and sense data 085C0001. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL ANXBFTH.DLL PROBLEM CONCLUSION: Transform Handler (TH) calls the DB service to delete the entry in the File Service (FS) catalog. DB, when attempting to delete an INRU entry,returns that catalog global name could be not deleted while related local file did. The TH did not handle this condition and ended with unexpected condition error. Now, the TH handle this event. PTRNBR: 2M04167 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: UNCATALOG_CM COMMAND DOES NOT WORK IN Q3 ENVIRONMENT. PROBLEM SUMMARY : The command CDM UNCATALOGCM cannot be used in Q3 (Host-Attached-Ws environment). If this command is invoked in this environment the User receives the message ANX1166 (the command cannot be used in this kind of environment). COMPONENTS CHANGED OR ENHANCED: ANX.MSG CDMCLT.EXE CDMSRV.EXE PROBLEM CONCLUSION: The command is now available and listed in message ANX1264. PTRNBR: 2M04168 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: ANXPRSTN.DOS NOT PRESENT UNDER DPACODE DIRECTORY. PROBLEM SUMMARY : NvDM/2 installation programs do not load the file ANXPRSTN.DOS under the directory PCACODE\DPACODE when installing a CC Server either as standalone or Host attached. COMPONENTS CHANGED OR ENHANCED: ANXF.LST PROBLEM CONCLUSION: Installation list upgraded to correct the occurrence. PTRNBR: 2M04172 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: LOG FILE OF AN EXT. INST. IS NOT CATALOGED AS UNIFORM TEXT FILE PROBLEM SUMMARY : The log file generated by an external install and automatically cataloged is in binary data instead of uniform text file. This does not allow the file to be read at host when retrieved. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The automatic log file is now cataloged as uniform text file. PTRNBR: 2M04178 APARNBR: PJ16758 PTFNBR: XR20465 EXTERNAL SYMPTOM: CID EXIT CODES MANAGEMENT PROBLEM SUMMARY : The codes FExx are treated as successful Do Reboot and don't call me back. This behavior is correct only for FE00 FE04 FE08 FE12 all the other must be unsuccessful. LCU already treats these as unsuccessful and at the CID Design meeting held in October 1994 it was committed to fix this in NetView DM platform agents. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: Only the architected FExx codes are treated as successful. PTRNBR: 2M04179 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: DECODE PROCESS ERROR. PROBLEM SUMMARY : Assume to SEND a resource of 4976 bytes from Host to node. The resource is an uniform text and it is compressed with NVDMLZW algorithm. The send operation ends at node with RC=08B1 000C. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The RC=08B1000C means that the decompression operation is failed at node. But the true problem is not due at the decompression routine, it is due at the write file operation. In fact the decompression routine receives a corrupted data file. This particular condition can be recreated with a resource of 4976 bytes and a header (containing the Global name) of 142 bytes. With this data sizes the Specific Server will work with two segments from Parser and Builder and with a SNADS buffer containing only the server object suffix. In this condition the bytes from Parser & Builder buffer to Read_Buffer is not copied correctly. The fix consists in testing when a segment is completely processed and the next SNA_Buffer will contain only the suffix. If it is the case, the 912 bytes are written suddenly in the Read_Buffer and the segment number increased of one. PTRNBR: 2M04180 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: TRACE DIRECTORY IS DELETED AFTER A REINSTALLATION PROBLEM SUMMARY : After a reinstallation, the directory TRACE is deleted. COMPONENTS CHANGED OR ENHANCED: SBODY.EXE PMSBODY.EXE ANXIISNA.EXE PROBLEM CONCLUSION: Problem corrected. The directory TRACE is not more removed. PTRNBR: 2M04183 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: PC HANGS WHEN 'TRANSMISSION QUEUE' IS REQUESTED PROBLEM SUMMARY : When CDM Catalog is starting and you click on 'Engine/Transmission Queues' before the Catalog window is filled with lines, the window for transmission queues appears and then the PC hangs. Reboot is necessary. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: When the CDM dialog is starting, 'Engine' items are now disabled until all the windows are displayed with the objects in. (The hang was due to a resource contention problem: too many queries to the database when the CDM dialog is starting.) PTRNBR: 2M04184 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: CM ACTION HANGS WHEN SERVER IS STOPPED AND RESTARTED PROBLEM SUMMARY : When an install action has been submitted, from a CC server, to a client, and the client starts to process it (the .CLI file has been created under the CMREQ dir) and, during the process the server is stopped by issuing the CDM STOP command, the request never completes. The SRVIFS continues to work completing the transferring of all files from the server to the client and the client installs correctly all the files, but if the server is started again by CDM START, client's status is RUNNING, the global name is in status SCHEDULED and the .CLI files is still present. The only way to recover is to issue a CDM STOP and CDM START on the client. COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.EXE ANXIFSRV.DLL ANXIFREQ.DLL PROBLEM CONCLUSION: The problem, now fixed, was due ANXIFS didn't accept more Client attach request from CC Server later a CDM STOP was issued on this last. PTRNBR: 2M04187 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: MSG ANX0109 IMPROPERLY ISSUED DURING AN INSTALL PROBLEM SUMMARY : This pmr has been opened because of pmr 8164x (customer cmc). The problem has been found at csd xr20334 (5) but it occurs also at level xr20254 (6). Initiate the procedure with name AAA.BBB (or AAA.BBB.CCC), then, while the procedure has still status SCHEDULED try to install the object AAA.BBB.REF.100. The install of AAA.BBB.REF.100 fails with message ANX0109 "The request was unsuccessful because its Object type is inconsistent with the Object Type of its associated component". NOTE: The problem occurs in both the cases:if the GRP does not exist yet and if the GRP already exist an it is the correct GRP for that object type. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.MAK PROBLEM CONCLUSION: The problem was caused in module ANXACPC2 during the check to verify if there were other global names with component name equal or greater of the object to be installed with different Object Type. This happen only if the entry of the checked object is SCHE and not when it is CATALOGED. The problem is solved by avoiding this check for entries scheduled when these entries are not related to a change management object. (i.e. when the STI token does not exist in the Global Name). PTRNBR: 2M04188 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: CC AND CDM AGENT ARE NOT STARTED WHEN TC RECOVERS. PROBLEM SUMMARY : In some situations when the Transmission Controller takes a time longer than usual to start (for instance after a power off, or when at the CC Server lots of queues are defined) CC and CDM Agent are not started by CDM START command. The following message is displayed: ANX0181: The Transmission Controller is not active. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The occurrence was due an API call performed by CLEANUP module before the Transmission Controller becomes active. PTRNBR: 2M04190 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: INVALID LEVEL CHECK DURING INSTALL OF UPD OBJECT PROBLEM SUMMARY : Problem found by CVP DIAGONAL. Installing an object A.B.REF.0 then an object A.B.UPD.0.1 everything works fine but trying to install A.B.REF.20000000 and then A.B.UPD.20000000.20000001, The install of the UPD object fails with the message ANX0182 (not enough memory) and the message ANX0105 (invalid level). COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.MAK PROBLEM CONCLUSION: The cause is due to a wrong variable definition for the token level. It was defined as FIXED(16) instead of FIXED(32) PTRNBR: 2M04191 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: WRONG RESTART BYTES COUNTER IN GENERAL SERVER PROBLEM SUMMARY : Assume a SEND from Host to node through an intermediate node and several line failures occurred during the task. In this scenario the restartability is not correctly performed after the second line failure. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The bytes count is initialized to zero only when the restart procedure is called at first time. PTRNBR: 2M04192 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: USER ABEND 33-12 AT HOST WHEN SENDING FROM NODE PROBLEM SUMMARY : Attempting a SEND from NvDM/2 to HOST results as USER ABEND 33-12 at NvDM/MVS. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem, now fixed, was due to two extra byte coded by Specific Server. PTRNBR: 2M04195 APARNBR: PJ16759 PTFNBR: XR20465 EXTERNAL SYMPTOM: SEND FAILS BECAUSE BUILD DOES NOT SUPPORT TURKISH CP PROBLEM SUMMARY : When the Build function is used with a Build profile containing the Description field on a machine with the Turkish country code (090) and Turkish codepage (857),the CCSID for the Description is not written in the catalog. The evidence of the problem is that when you issue a Send for this object it fails with the message: ANX0698: (E) A SNA/FS Server operation failed with return code = 085A0000 COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL ANXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: The cause of the problem is that the Turkish code page 857 is not included in the CCSID table used by the Catalog (and the Build) function. The problem is solved including also this code page in the list of the supported code pages. PTRNBR: 4U00035 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: LET NVDM/2 DOS CLIENT WORK ON DOS HIGHER THAN V6.0 PROBLEM SUMMARY : Getting error when trying to use NvDM/2 DOS Client on a DOS higher than 6.x The log into ERROR.DAT is the following: . Error detected in NetView DM/2 CM component. The error was generated in module ANXCCCSR. Return codes were: Primary=20, Secondary=0, Auxiliary=101. Additional Data : 41 4e 58 43 43 43 53 52 30 30 30 31 41 4e 58 43 ANXCCCSR0001ANXC 43 43 53 52 20 20 20 20 20 20 20 20 00 00 00 00 CCSR .... 00 00 00 00 14 00 00 00 65 00 49 66 73 53 74 61 ........e.IfsSta 72 74 52 65 71 00 00 00 00 00 00 00 00 00 00 00 rtReq........... COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMEXE.EXE PROBLEM CONCLUSION: The problem was due unsupported DOS version by NvDM/2 that now does. PTRNBR: 5000719 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: SYSTEM ABEND '2' DURING A SEND WITH DIALOGS OPENED PROBLEM SUMMARY : System abend '2' sending a file cataloged compressed to be decompress at the Target. At the Target a trap occurs with the following information: ' A program caused exception C0000005 at 13776B88. ' ' Due to insufficient stack space, the exception was ' ' not dispatched. ' ' ' ' ANXBFTH.DLL 0006:0FC34BD2 ' ' ' ' CS:EIP 8FB7:00008015 ' ' CSLIM 000085F1 ' ' ' Under FSDATA directory the file FSF... is created compressed and under FSFTMP directory the file TH0.... is created decompressed. After the trap the Change Controller is inactive. If the dialogs are inactive, the send ends successfully COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The problem was due to the fact that every time the routine that decompress / compress a file was called from the ANXBFTH.DLL a stack of memory was allocate for it but at the end of this thread ,when the semaphore of synchronization is cleared, this stack was deallocated from the calling thread (ANXBFTH) so the compress/decompress thread does not have anymore the stack to close its activity and traps. This situation happens in particular on machines with few RAM memory. Now the problem is solved because is the Beginthread that allocate automatically the stack for the compress/decompress thread and the Endthread releases it. PTRNBR: 5001208 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: NvDM/2 V2.1 OS/2 CC CLIENT INSTALL. FAILS AND HANGS ON REBOOT PROBLEM SUMMARY : Scenario: from a CC Server, install a NvDM/2 V2.1 OS/2 CC Client on a workstation. This works fine for the first attempt and the first three reinstall, for instance to refresh code or to reconfigure. The external symptoms is the installation completed, then the CC Client reboot and then hangs on IPL. The cause of the hang is a lack of NvDM/2 statements in CONFIG.SYS. COMPONENTS CHANGED OR ENHANCED: BODY.EXE SBODY.EXE PROBLEM CONCLUSION: Fixed. PTRNBR: 5001246 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: UNRECOVERABLE ERRORR WHEN FILESPECLIST SECTION CONTAINS WRONG DIR PROBLEM SUMMARY : Assume to issue the following command to create a change file: CDM BUILD C:\PROFILE\PROVA.PRO FS:PROVA.PKG Where C:\PROFILE\PROVA.PRO is the following: . targetdir=c:\SNeF . section catalog begin objecttype=software globalname=S.N.e.F.ref.1 end . section filespeclist begin SNUF\ end . And . c:\snuf is an existent but empty directory . The following error is logged: . ** NetView DM/2 logged at 12:17:24 12/05/1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXEFCBL. Return codes were: Primary=6, Secondary=14, Auxiliary=8. Additional Data : 41 4e 58 45 46 43 42 4c 30 30 30 31 50 41 43 4b ANXEFCBL0001PACK 00 00 00 00 43 68 65 63 6b 20 50 61 63 6b 06 00 ....Check Pack.. 0e 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ............ ............ ............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 ........ .ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 12:17:25 12/05/1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXECCBX. Return codes were: Primary=11, Secondary=0, Auxiliary=0. Additional Data : 41 4e 58 45 43 43 42 58 30 30 30 31 41 4e 58 45 ANXECCBX0001ANXE 43 43 42 4e 4e 64 6d 42 75 69 6c 64 43 68 61 6e CCBNNdmBuildChan 67 65 0b 00 00 00 00 00 00 00 00 00 00 00 00 00 ge.............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ............ ............ ............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 ............ ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: The occurrence was due an invalid check on the input filename speclist, now fixed. PTRNBR: 5001334 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: NVDM/6000 - NVDM/2 DISTRIBUTION PROBLEM SUMMARY : NvDM/2 node send a resource to NvDM/6000 node. The send fails with return code 08120011 (lack of memory on receiver), then NvDM/2 node retries the SEND infinitely until space/memory becomes available. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: Since NvDM/2 is not designed to manage a determined number of retries, when the sense code 08120011 is returned,upon a SEND task and to prevent looping with remote node, no retries are attempted. . NOTE: the aforementioned retries do not matter to those customizable, via user exit routine, for LU-LU allocation. There is not way to customize retries upon the above failing scenario. . PTRNBR: 5001335 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: NVDMCLT MUST NOT ASK THE A DRIVE WHEN USING NetBIOS FOR TCP-IP PROBLEM SUMMARY : During the pristine scenario, using NetBIOS for TCP-IP as transport, the installation asks for inserting the diskette in the drive A. COMPONENTS CHANGED OR ENHANCED: BODY.EXE PROBLEM CONCLUSION: The check for NETBIOS now generate just a warning in case of non IBM NetBIOS detected. PTRNBR: 5001343 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: RANDOMLY, TRANSMISSION CONTROLLER TRAPS WHILE STOPPING THE PRODUCT DURING A TRANSMISSION PROBLEM SUMMARY : Stopping the NvDM/2 during a transmission, in a random way,the Transmission Controller traps or the Communication Manager is stopped. . A program generated an access violation at 00129535 ANXSNADS.EXE 0001:74d36815 P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=0000000C EBX=0000945C ECX=00000000 EDX=00000000 ESI=00000000 EDI=0000000C DS=009f DSACC=00f3 DSLIM=0000042a ES=0000 ESACC=**** ESLIM=******** FS=150B FSACC=00F3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=0097:00009535 CSACC=00FB CSLIM=0000AEFC SS:ESP=8DB7:00008BD2 SSACC=00F3 SSLIM=0000BFFF EBP:00008BDE FLG=00012206 COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The TRAP was generated by Receiver Manager component of the Transmission Controller when stopped while writing upon an active transmission. Now, the Transmission Controller manages to allow its processes to complete work before to STOP. PTRNBR: 5001344 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: ANX0262 MESSAGE VARIABLES NOT DISPLAYED PROBLEM SUMMARY : The message ANX0262 with no valid values in the various fields, only the %1,%2,%3,%4, appeared when NCBS was set to 13 or less. Reference: PMR 1X467 B468 C000 COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE ANXPULAG.EXE PROBLEM CONCLUSION: Fixed. PTRNBR: 5001357 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: INCONSISTENT DEFAULTS ON DISKCOPY PROGRAMS PROBLEM SUMMARY : It appears that the various diskcopy programs have different defaults for the source drive: . NVDMCOPY default, NVDMCOPY drive NVDMDCPY default, A: drive NVDMDOC default, NVDMDOC drive COMPONENTS CHANGED OR ENHANCED: NVDMDCPY.EXE PROBLEM CONCLUSION: The NVDMDCPY has been changed according to the others. PTRNBR: 5001358 APARNBR: PJ16760 PTFNBR: XR20465 EXTERNAL SYMPTOM: NVDMENV PROGRAMS IS NOT ENABLE TO OS/2 WINDOWS. PROBLEM SUMMARY : Suggested to enable NVDMENV. COMPONENTS CHANGED OR ENHANCED: NVDMENV.EXE PROBLEM CONCLUSION: The suggestion has been implemented. PTRNBR: 5001372 APARNBR: PJ16761 PTFNBR: XR20465 EXTERNAL SYMPTOM: TRAP OCCURS IF DPATH IS LONGER THEN 254 PROBLEM SUMMARY : A trap (doscall1.dll) occurs every time the DPATH in the CONFIG.SYS is longer than 254 COMPONENTS CHANGED OR ENHANCED: NVDMINST.EXE NVDMCLT.EXE NVDMFPIN.EXE PROBLEM CONCLUSION: Fixed. PTRNBR: 5001380 APARNBR: PJ16761 PTFNBR: XR20465 EXTERNAL SYMPTOM: WRONG INSTALLATION OCCURS FOR PREDEFINED INSTALLATION TARGET LONGER THAN 130 CHARACTERS. PROBLEM SUMMARY : If an Installation target is already defined with a path longer then 130,an install of a global name matching this Installation target cause the software to be installed on a wrong path. The actual installation path is the real path truncated at the 130th character and concatenated with the 'GRP' string. COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL PROBLEM CONCLUSION: Problem fixed. PTRNBR: 5001407 APARNBR: PJ16761 PTFNBR: XR20465 EXTERNAL SYMPTOM: THE MESSAGE ANX0253 DIDN'T POINT THE USER TO THE RIGHT ACTION PROBLEM SUMMARY : This PTR to receipt a suggestion from Level 2 of Support to improve ANX0253 message text and its related help to reach better usability by Customers. COMPONENTS CHANGED OR ENHANCED: README.TXT ANX.MSG ANXH.MSG PROBLEM CONCLUSION: The message has been modified and the help enriched. PTRNBR: 5001415 APARNBR: PJ16761 PTFNBR: XR20465 EXTERNAL SYMPTOM: NVDMBDSK PUT INVALID VALUE IN ADAPTER FIELD PROBLEM SUMMARY : When using the NVDMBDSK utility to create a NvDM/2 client boot diskette,the AdapterNum field is incorrectly set to a tilde,'~', instead of the assigned 0 value. COMPONENTS CHANGED OR ENHANCED: NVDMBDSK.EXE PROBLEM CONCLUSION: Fixed PTRNBR: 5001457 APARNBR: PJ16761 PTFNBR: XR20465 EXTERNAL SYMPTOM: CANNOT DELETE INSTALL HISTORY IN THE CATALOG PROBLEM SUMMARY : Trying to delete the install history on CC Server from its DIALOG, but the attempt failed with: ANXE5101 - The operation failed because of an internal error. Please contact your Product Administrator. rc='0', reason='11'. Tried CDM STOP and brought down the Dialog, but after the restart, still getting the same error, and can not delete the install history on CC Server. COMPONENTS CHANGED OR ENHANCED: ANXCSCD9.BND ANXEFAPI.DLL ANXCMSRV.EXE PROBLEM CONCLUSION: The problem, now fixed, was due to incorrect managing of a status returned from a catalog service. PTRNBR: A001056 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: REMU WITH SNACR=100D0002 WHEN LINK FAILS PROBLEM SUMMARY : Assume to attempt a SEND of a resource from HOST to node. After sending data,the link fails. When the link restarts the transmission terminated with 100D0000 error at host, because the phase requested by node during the restart process was not in pending status at host. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: In the scenario described above, when the host doesn't found the phase in pending status, it sends to node a REMU with RC=100D0002 (new SNACR: Request temporarily inconsistent). This new SNACR setting is the fix required a t NvDM. NVDM HOST COREQUISITE: ====================== This fix requires APAR No. PN55403 to be implemented on NvDM/MVS R5, COMPID 568501601 PTRNBR: 2M04142 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: ERROR ISSUING CATALOG COMMAND FROM DIFFERENT SESSIONS PROBLEM SUMMARY : Assume to perform the following sequence of commands: start a.cmd start b.cmd Where a.cmd is cdm catalog a.a.a c.pkg cdm catalog b.b.b c.pkg and b.cmd is cdm catalog c.c.c c.pkg cdm catalog c.c.c c.pkg The message 'ANX0310: CATALOG failed because the catalog entry ' ' already exist. ' The message is issued randomly even if the entry is not an already existing one. COMPONENTS CHANGED OR ENHANCED: ANXCSCD3.BND PROBLEM CONCLUSION: The cause of the problem in the wrong process to create the INDEX field in the database Services. PTRNBR: 2M04144 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: INSTALL FAILS FOR GLOBAL NAME WITH TOKEN .GRPTEST PROBLEM SUMMARY : Installing an object whose global name contains a token beginning with GRP string, if the install fails, a 'dirty' entry remains in the NvDM/2 Catalog. In this situation the correct message with the explanation of the reason of the failure of the install should be issued and the object should remain in CATALOGED status. COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL ANXCSCDL.BND PROBLEM CONCLUSION: After any INSTALL that fails, the NvDM/2 Product now update correctly the Change Management data corresponding to the failing object. PTRNBR: 2M04152 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: SEINST INVOCATION FAILS IF FORMAT C DRIVE IS REQUESTED PROBLEM SUMMARY : Failing scenario . 1st step: ========= The maintenance system on the D drive is installed successfully (OS/2 2.1, NTS/2 and NvDM/2 CC Client). . 2nd step: ======== The production installation starts (OS/2 2.1 with format partition option, NTS/2 and NvDM/2 CC Client). on the C During the format of C drive, SEINST fails because of the C drive is locked. . COMPONENTS CHANGED OR ENHANCED: BODY.EXE SBODY.EXE PROBLEM CONCLUSION: Fixed PTRNBR: 2M04155 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: RUNNING ANXWCLOA DECREASES WINDOWS PERFORMANCE PROBLEM SUMMARY : After having installed NVDM/2 CC Client on a DOS machine with MS Windows, ANXWCLOA is installed and run any time that windows starts. This program make all Windows applications much slower. COMPONENTS CHANGED OR ENHANCED: ANXWCLOA.EXE PROBLEM CONCLUSION: A loop was found in the way in which ANXWCLOA enquiries the network. Once the loop is eliminated better performances are measured. PTRNBR: 2M04156 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: WINDOWS AGENT DOES NOT MANAGE CORRECTLY MS NETBIOS PROBLEM SUMMARY : If Microsoft (MS) Netbios has been loaded,when Windows started, a message is shown by ANXWCLOA saying that there has been a SUBSYSTEM NETWORK ERROR :RC 0x:8400 COMPONENTS CHANGED OR ENHANCED: ANXWCCOM.DLL PROBLEM CONCLUSION: The return code from Netbios was not correctly managed, now corrected. PTRNBR: 2M04158 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: WRONG TEMPLATE FILE PATH FOR NVDMUFM UTILITY. PROBLEM SUMMARY : problem found by ROYAL INS SOFTW PMR 0630X Issuing the command: NVDMUFM d:«abcd«ef«pippo.tmp d:«1234«567890«filename.txt the message: "ANX01634: Unable to access the 'D:«ABCD«EF«890«pippo.tmp' file" is displayed. i.e. if the path for the template file is shorter than the path specified for the PWS unique file, the template path is completed with the last characters of the PWS unique file path. COMPONENTS CHANGED OR ENHANCED: NVDMUFM.EXE PROBLEM CONCLUSION: Variable 'SPLIT spt' not reset before calling xx_splitpath() function. PTRNBR: 2M04159 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: RUNTIME ERROR, PRIMITIVE SYSTEM FAILED PROBLEM SUMMARY : A Customer in Saudi Arabia running NvDM/2 V2.0 at CSD XR20354 experiences the following error when working with CDM Dialogs: Runtime Error: Primitive System Failed. The error comes up in the following failing scenario: a - CDMD b - Logon to database O c - Click on ENGINE R d - Click on All Pending Requests... after a little, the following message is prompted: Runtime Error: System Primitive ... Click OK on message From now on, the Customer is not able to work anymore with CDM Dialogs. Once the Customer close and open again the CDM Dialogs, It is prompted that CDM Dialogs are already active even thought closed. This strange condition is due to thread 3 of CDMD that upon the previous described failure remained in BLOCK status. To recover from this condition,the Customer need to IPL the machine or to kill the PID, CDMD related, that has the thread in BLOCK status. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXEFAPI.EXE PROBLEM CONCLUSION: The occurrence was raised by wrong handling of zero bytes field into empty CMF files, now fixed. PTRNBR: 2M04169 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: IMPROVE ERROR LOGGING AND AVOID MSG ANX0082 PROBLEM SUMMARY : Improve error logging in the NVDNLZW compress operation. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: This fix improves error logging in case of NVDMLZW compress error. Now the error log contains also this info: - the name of file to be compress. - the name of temporary file (TH0xxxxx) used from NVDMLZW to store the compressed resource. - the return code of NVDMLZW.EXE module. More, this fix corrects also the wrong issuing of message ANX0082 instead of ANX0131 at the end of a file updating operation. PTRNBR: 5001261 APARNBR: PJ14863 PTFNBR: XR20465 EXTERNAL SYMPTOM: The send and install function fails with sense code 100b0005. PROBLEM SUMMARY : When a Send and Install request with removability option is issued from the host and this install request involved objects for which will be produced some secondary effects the operation fails at the Host site with the sense code 100b0005. COMPONENTS CHANGED OR ENHANCED: For this fix the ANXLASD.DLL has been changed. PROBLEM CONCLUSION: The problem was due to an incorrect work of Parser and Builder. The routine is the PUT_FIELD command. This wrong behavior produce that in the report that will be sent to the Host the '1212' structure (Agent object) is greater of 1 bytes of the '1573' structure that contains it.This is not possible so the Host issue the sense code 100b0005. PTRNBR: 2M04175 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: DIRECTORY NOT REMOVED AFTER CDM REMOVE ACTION PROBLEM SUMMARY : Assume the following scenario: 1) A change file profile is created specifying in the target dir keyword a directory that doesn't exist. 2) A change file is created using the profile as per item 1. 3) Thus, an INSTALL of the change file as per item 2 is successfully attempted (i.e. the directory that didn't exist was created and the files to be installed were put under it). At this point a REMOVE of the change file as per item 2 was attempted with the following results: the files were correctly deleted, BUT THE DIRECTORY IS NOT REMOVED. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The problem is solved by adding in CMF file a field indicating if, at the install time, the target dir was created. According by the value of this field the target dir is removed at the remove time. PTRNBR: 2M04181 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: ANXCKPUQ.DLL TRAP WITH LOCKED FILE PROBLEM SUMMARY : When installing a Change File that replaces at least one locked file, randomly, the CDM agent traps. This problem occurs only on Client PWS. System Error - CDM Agent SYS3175-------------------------------------------- A program generated an access violation in 19c1of88 A program generated an access violation in 19c1of88 ANXCKPUQ.DLL 0005:01290266 P1=00000008 P2=00005390 P3=xxxxxxxx P4=xxxxxxxx EAX=00000000 EBX=0000ABE7 ECX=000B0015 EDX=00000000 ESI=0000FB3E EDI=0000FB53 DS= 009F DSACC= 00F3 DSLIM= 0000FFFF ES= 009F ESACC= 00F3 ESLIM= 0000FFFF FS= 150B FSACC= 00F3 FSLIM= 00000030 GS= 0000 DSACC= **** DSLIM= ******** CS:EIP= CE77:00000C30 CSACC= 00FB SCLIM= 000038F7 SS:ESP= 009F:0000F518 SSACC= 00F3 SSLIM= 0000FFFF EBP = 0000F15A FLG= 00012246 COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: A build error caused a dis-alignment in a module. PTRNBR: 2M04182 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: IMPROVE MESSAGING FOR ANXBCP00 PROBLEM SUMMARY : When the anxcscd1 module returns unexpected condition to the anxbcp00 module, no messages indicating that the catalog cannot be opened is logged. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: When the anxcscd1 returns 'unexpected condition' the message 1015 is issued. PTRNBR: 2M04189 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: INITIATE FAILS WITH 08380012 SENSE CODE PROBLEM SUMMARY : A SEND-INITIATE fails with sensecode 08380012. In particular this happens when performing this operation several times for DIFFERENT objects. COMPONENTS CHANGED OR ENHANCED: ANXCSCD4.BND PROBLEM CONCLUSION: This occurrence was due an internal Agent instances counter that was not reset. PTRNBR: 2M04194 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: FOR LU ALIAS DIGIT AS FIRST CHAR MUST BE ALLOWED PROBLEM SUMMARY : Currently a check is made on the LU ALIAS for the first character not to be a digit, while CM/2 allows a LU ALIAS definition starting with a digit. The problem occurs while trying to define a remote destination. COMPONENTS CHANGED OR ENHANCED: ANXEDTSN.DLL ANXEFAPI.DLL PROBLEM CONCLUSION: Check modified to allow a digit as start character of a LU ALIAS definition. PTRNBR: 2M04196 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: ANXIFS TRAP D DURING CM/2 OR TCP/IP INSTALLATION PROBLEM SUMMARY : Typically, the problem occurs when installing TCP/IP 2.0 or CM/2 1.11. Rebooting the PC will allow the process to continue, but it may have the error again. There does not seem to be a particular point in the installation process that causes this error. . The trap panel with NetView DM/2 at xr20354 level is TRAP 000d ERRCD= 0000 ERACC= **** ERLIM= ******** EAX= a510ffff EBX= 00007990 ECX= 000008bf EDX= 00000101 ESI= 7bc5ffff EDI= 000079a8 EBP= 0117538c FLG= 00012246 CS:EIP= 0b48 : 0000228f CSACC= 009b CSLIM= 0000559c SS:ESP= 0030 : 00004362 SSACC= 1097 SSLIM= 000046e3 DS= 0b40 DSACC= 0093 DSLIM= 000001df CR0= 8001001d ES= 08bf ESACC= 00f3 ESLIM= 00007fff CR2= 000df000 FS= 0000 FSACC= **** FSLIM= ******** GS= 0000 GSACC= **** GSLIM= ******** THE SYSTEM DETECTED AN INTERNAL PROCESSING ERROR AT LOCATION ¡¡ 0160 : fff5ddbc - 000d : 9dbc 60000 , 9084 . INTERNAL REVISION 6 . 653 DATE: 01/11/94 * TRAP * * INFORMATION * . COMPONENTS CHANGED OR ENHANCED: ANXIFCOM.IFS PROBLEM CONCLUSION: The problem was due to a wrong parameter in a memcopy call during a QUERY_EA_SIZE operation via a DosFSCTL to ANXIFCOM IFS. PTRNBR: 2M04197 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: WRONG CHECK ON IFS STATEMENTS FOR ACTIVATE PROBLEM SUMMARY : The logic used to add the Activate statements before the reboot in the config.sys consist of adding the two statements after the first IFS statement (different from the NVDM/2 ifs) found. . This can cause problems in case the IFS statement is not the HPFS the HPFS386 statement. . The logic must be changed in ANXACCWC so that the Activate Statements are added after the first HPFS statement. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: The check has been changed so that the two statements are not added after the first encountered IFS statement but after the first IFS statements containing the substring HPFS. PTRNBR: 2M03763 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: INCORRECT IBMNVDM2.INI WRITING USING ANXEDINI PROBLEM SUMMARY : ANXEDINI writes an IBMNVDM2.INI file with TransformParam = ' ' when TransformAlgo = NVDMLZW It should be TransformParam = '' (null) otherwise the product does not properly work COMPONENTS CHANGED OR ENHANCED: ANXEDINI.EXE PROBLEM CONCLUSION: Corrected the malfunctioning. PTRNBR: 2M03890 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: REMOVE IN SERVICE DOES NOT WORK IN PARTICULAR CONDITIONS PROBLEM SUMMARY : The following sequence lead to error: INSTALL Obj in ACTIVE with Removability REMOVE Obj REMOVE Obj in SERVICE COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The problem was due to a wrong internal call. PTRNBR: 2M03988 APARNBR: PJ15976 PTFNBR: XR20465 EXTERNAL SYMPTOM: SOME TIME CHANGE CONTROLLER ENDS AFTER A CDM STOP COMMAND PROBLEM SUMMARY : Issue the following commands on the Server: CDM INSTALl PIPPO.I.REF.1 FOR I=1,30 CDM STOP SLEEP 60 CDM START Some times after that the CDM STOP is issued, the Change Controller ends because of errors, the following error and message are logged: ************* ERROR.DAT ***************** ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 13:57:29 23/11/1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXAAPM2. Additional Data : 41 4e 58 41 41 50 4d 32 30 30 30 34 3e 00 00 08 ANXAAPM20004>... 41 4e 58 43 53 30 53 42 41 4e 58 41 41 50 4d 32 ANXCS0SBANXAAPM2 41 4e 58 43 53 50 53 35 10 00 14 00 5f 00 92 09 ANXCSPS5...._.’. af 00 e2 09 af 00 c0 ca af 00 0b 00 ff ff ff ff ¯.â.¯..ʯ....... 00 00 00 00 00 00 00 00 4e 00 ........N. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 13:57:30 23/11/1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXAAPM2. Return codes were: Primary=16, Secondary=20, Auxiliary=95. Additional Data : 41 4e 58 41 41 50 4d 32 30 30 30 31 41 4e 58 43 ANXAAPM20001ANXC 53 50 53 35 20 20 20 20 20 20 20 20 20 20 20 20 SPS5 20 20 20 20 10 00 14 00 5f 00 00 00 00 00 00 00 ...._....... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 3e 00 00 08 41 4e 58 43 53 30 ......>...ANXCS0 53 42 41 4e 58 41 41 50 4d 32 41 4e 58 43 53 50 SBANXAAPM2ANXCSP 53 35 10 00 14 00 5f 00 92 09 af 00 e2 09 af 00 S5...._.’.¯.â.¯. c0 ca af 00 0b 00 ff ff ff ff 00 00 00 00 00 00 .ʯ............. 00 00 4e 00 ..N. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ÍÍÍÍÍÍÍÍÍÍÍ***********ÍMESSAGE.DATÍ****************ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 13:57:31 23/11/1993 ** ANX0277: (I) The CDM Agent has been immediately stopped by the user. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 13:57:33 23/11/1993 ** ANX0074: (E) The Change Controller ended because of errors. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ COMPONENTS CHANGED OR ENHANCED: The component changed is the ANXCMSRV.EXE. PROBLEM CONCLUSION: The problem was due to the fact that sometime when a CDM stop command was issued the operating system returns the return code 95 (error_interrupted) to the DosSem Wait api and this situation was managed as an error from the product so the message anx0074 was issued instead of the message anx0072. Now a correct management of this error is executed so the correct message is logged. PTRNBR: 1000092 APARNBR: PJ16016 PTFNBR: XR20465 EXTERNAL SYMPTOM: WRONG MANAGEMENT OF OS2 ERROR WHEN CREATING DIRS PROBLEM SUMMARY : In case an error is found in setting Extended Attributes during a creation of a directory, the OS/2 operating system gives back a return code that unfortunately is not saved. Thus the OS/2 error that is logged is without meaning. COMPONENTS CHANGED OR ENHANCED: LDSR.EXE PROBLEM CONCLUSION: The problem has been fixed. It was due to an uncorrected saving of the return code. PTRNBR: 1000093 APARNBR: PJ16016 PTFNBR: XR20465 EXTERNAL SYMPTOM: EAS WRONG MANAGEMENT IN CREATING NEW DIRS PROBLEM SUMMARY : When creating a dir that is a root or that does not exist on the server that follows a directory creation with EAs, an error in setting the EAS on the receiver may happen. This is due to the fact that the receiver asks to set EAs for the new dir and at the same time the distributor cannot find and send these EAs. COMPONENTS CHANGED OR ENHANCED: LDS.EXE PROBLEM CONCLUSION: The problem has been fixed. ************************************************************************ * The following information provides details about the APARs fixed by * * previous CSDs (XR20273,XR20276,XR20302,XR20313,XR20334 and XR20354) * * cumulated in this current CSD issue * * * * Netview Distribution Manager/2 Version 2.0 * * * ************************************************************************ PTRNBR: 5001275 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: THE TRANSMISSION CONTROLLER TRAPS PROBLEM SUMMARY : Problem description: In the random way the Transmission Controller traps during a stress test of 64 send from two RA to 10 servers. In the trap the EIP = 104 and the CSLIM = E1A8. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The Transmission Controller deletes the SAF files, mainly, in two steps: 1) Delete the FCB (file control block) for that SAF files (LSDFM0CL) 2) Delete the SAF file (LSDFM0ER). In particular stress condition, these two operations can be performed from two different General Server threads. Of course, in this case, each common data operation have to be included in a DosSemRequest and in a DosSemClear. The TRAP is due because a pointer updated in the Delete FCB module is also handled in the Delete SAF module without a DosSemRequest. PTRNBR: A001043 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRANSMISSION CONTROLLER DOESN'T PROCESS THE LAST RETRIEVE OF 6 RETRIEVE PLANS FROM HOST PROBLEM SUMMARY : The Customer operates 6 RETRIEVE plans between host NvDM and node NvDM/2 about 11 times per a day. Sometimes only 5 files are fetched at node so the relative host plan remain pending. At node the msg ANX0132 (file fetched) for 6th file is not issued. At host the msg NDM01061 (file pending) is the last msg for 6th file. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: When a distribution arriving to NvDM/2, the Receive Manager task communicates this to the Scheduler task. The Scheduler task actives the Router Director task to process the distribution arrived. In the customer scenario there is a timing problem among these tasks. In fact when the Router Director task terminated to process the 5th distribution sent from host, it initiates the close task procedure. In this time the 6th distribution arriving so the Receiver Manager task communicates this to the Scheduler task but never the Router Director is started. Therefore, in the particular distribution plans it's possible that a new entry is added to Router Director Queue when the Router Director task terminating. Now,when a new entry is added to Router Director Queue but the Router Director task terminating there are two global constants that 'photograph' this situation: 1) the number of entries in the Router Director Queue 2) the number of the active Router Director tasks (0 or 1). In this case the two constants are respectively set to 1 and 0, with these two values a new Router Director task must be activated. PTRNBR: A001046 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: LOOP IN TERMINATING ROUTER/DIRECTOR TASK PROBLEM SUMMARY: During a series of RETRIEVE operations from host, the NvDM/2 node detects the following errors: ANX0630 ========> error in DosRead ANXSNQDF.SNA file. ANX0791 ========> error in deleting transmission queue entry. After these errors the TC remains in a loop condition. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The TC loops in the following way: Router Director task is called to process an entry in its queue. Router Director task ends because no entry found. Router Director task is called to process an entry in its queue. ..................................................... ..................................................... This inconsistency is due at the previous errors during SNA files handling (ANX0630 and ANX0791 messages into the Message.dat file). If the SNA files handling error occurs,this fix avoids the TC loop. Once this fix is implemented, to recover from the above described loop,restart the TC to allow it to attempt to clean up the queues. If this action is not enough, the SNA files must be replaced with those .BAK one (available under TCDATA directory) and reconfigured. PTRNBR: 2M03468 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: ABEND DURING UNSUCCESSFULL INSTALL IN SERVICE WITH REMOVABILITY YES PROBLEM SUMMARY : If an error occur during the Section Install Processing of a change file (a program error for example) and also a FileSpecList Section is present and the Install is Removable in Service or Trial area the CDM Agent goes down with MSG ANX00279 and no Error Log. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: An error has been found during the AutoRemove process of the FileSpecList files already installed when the error take place in the Install Section. PTRNBR: 2M03872 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: TIMING OF CANCEL REQUEST DOESN'T WORK PROPERLY. PROBLEM SUMMARY : When a Request is in Waiting For Time status and it is cancelled the CANCEL request is accepted but the cancelled request remain Waiting For Time up to the original execution timing. Also the Resource in the Catalog remains scheduled for the addressed Workstation. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Now the Request is cancelled immediately by the Change Controller without waiting for the Execution Timing is expired. PTRNBR: 2M03980 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRANSFORMATION,INFO MESSAGE IF COMPRESSION IS NOT EFFICIENT PROBLEM SUMMARY : When sending an object with NVDMLZW and the algorithm returns 'no efficient compression' return code, an info message should be logged. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The Specific Server, if specified, calls the NVDMLZW algorithm to compress an object before sending the file. It's possible that the output compressed object is bigger that input file, so the Specific Server decides to send the file not compressed. With this fix the Specific Server issued the following new message: ANX0292(I): The NVDMLZW algorithm is not efficient to compress the file <name file> related to Global Name <name>. PTRNBR: 2M04027 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: NO HOST RETURN CODE AFTER UNSUCCESSFULL DECOMPRESS PROBLEM SUMMARY : If a compressed object is sent from host and the decompress algorithm fails, the generic message ANX0170 is stored at node but the Host does not receive any error message. On the IOF console you can only see the rc 0 for the successfully Send. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: This fix changes the Specific Server action during a store operation. In fact, now, if a compressed object is sent and the decompress algorithm fails at the target node, the file is not catalogued into FS Catalog and a report is sent to request originator with the Specific Server error 08B1 000C (Decompression data object exception). The SNA return code 08B1 000C will be displayed on IOF console. . The 'System Action' for messages ANX0168, ANX0169 and ANX0170 are changed in: 'The operation has not been completed; processing continues with other requests. The request originator is notified with a report.' PTRNBR: 2M04042 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: ANX0148W,DISK IN DRIVE A WARNING MESSAGE PROBLEM SUMMARY : When the IBM2FLPY.ADD line is commented out to logically remove the diskette drive, an ACTIVATE fails with msgANX0148I 'In drive A: there is a disk inserted', even with no disk in the drive. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: After a fix by OS/2 NetView DM/2, now manage the new return code from the function used to see the status of the drive. The related OS2 APARs are: PJ10930 and PJ11016. PTRNBR: 2M04048 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: NODE FILE SERVER OPERATION AUTHORIZATION PROBLEM SUMMARY : Assuming the following scenario: Focal Point (NVDM) send a resource with Replace option to its node. This Send operation fails at node with RC=08A50002 (user not authorized) but the Focal Point is always authorized at any FILE SERVER operations. COMPONENTS CHANGED OR ENHANCED: AMXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: The problem was due to an incorrect check of the HOST name that was 7 character long instead of 8 as expected by error. PTRNBR: 2M04096 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: SPECIFIC SERVER DOES'T CONSIDER '0A'(LF) AS END OF A RECORD PROBLEM SUMMARY : Assuming to attempt a SEND,from node to host,of a TXT file. This file contains only '0A' (LF) at end of same records instead of '0D'(CR) '0A'(LF). The Send operation fails with: ANX1262: Send failed because it could not transform the object between fixed and variable formats. ANX0698: SNA/FS Server ended with 085A 0000. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The Specific Server didsn't consider the '0A' as end of a record. When Specific Server calculates the records length it wrongs the max record length and this generated the problem. Now, the Specific Server considers the '0A' as end of a record. . REMARK: ======= The origin object size and the target one could be, from now on, different. In fact,at the target site the Specific Server adds at the end of record two characters 0D and 0A, where it finds 0A. In this way the Specific Server works like an editor that adds 0D 0A at the end of the record when the file is saved. PTRNBR: 2M04098 APARNBR: PJ14202 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRAP IN ANXLUSER.DLL WHEN HANDLING MESSAGES ORIGINATED BY TRANSMISSION CONTROLLER PROBLEM SUMMARY : The ANXLUSER.DLL traps when referencing the message variables of messages originated by the Transmission Controller.The trap is originated because the ANXLUSER parameters are reversed in the call. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL ANXSNADS.EXE PROBLEM CONCLUSION: The Transmission Controller (TC) now call the ANXLUSER with the correct pascal convention. The Message services now doesn't call the ANXLUSER any more when the msgid is 0 (this means that the message was originated by the TC) PTRNBR: 2M04102 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDM/2 REBOOT NOT SAVING OS/2 DATA PROBLEM SUMMARY : When modifing the DeskTop using a REXX procedure invoked by the NetView DM/2 agent that at the end asked also for the reboot, occurs that after the reboot some changes were not reported to the DeskTop. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXCMPMC.EXE PROBLEM CONCLUSION: THE DOSHUSTDOWN that is performed before the Device Driver call to the Send Event that perform the CAD sequence flush all buffers of the file system but this is not enough to guarrantee that also all the other update to the WPS files are done. We found that the CTRL-ALT-DEL sequence give the responsability of the actual ShutDOwn to the SessionManager (In case the WPS is UP) and therefore the DOsHustDown is called by the Session Manager after all WPS files has been updated. The simple solution was to avoid to issue the DosShutDown. In this way we completely rely on the CAD sequence to perform a correct shutdown of the system. PTRNBR: 2M04105 APARNBR: PJ13837 PTFNBR: XR20354 EXTERNAL SYMPTOM: INITIATE,BACKSLASH TRANSLATED TO BLANK ON NODE SIDE PROBLEM SUMMARY : The problem was detected by customer VERS BUNDESL. WIEN. Backslash in PROCDATA field on INITIATE PROCEDURE is translated to blank when submitted to NVDM/2 . The backslash is entered on NVDM panel ACSGCCRT in field PROCDATA. the problem occurs on non US host codepages. NVDM/2 expects X'E0' and depending on NLS codepage O_DIARESIS_CAPITAL or CEDILLA sign may circumvent. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Change controller always calls ANXCRPG4 to translate the INITIATE parms string from EBCDIC to ASCII without looking at the codepage in which the string is encoded. Now the function Anx_Translate_From_CP_to_CP is called instead of ANXCRPG4. The backslash char will be well translated if it is encoded at the host with one of the following values: Host-CCSID BackSlash ========== ========= 273 'EC'X 500 'E0'X PTRNBR: 2M04106 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDMIDOS STARTS AND FAILS IF START FROM THE 14 DISK PROBLEM SUMMARY : If the NVDMIDOS is started from a diskette different from the DOS CC Client installation diskette the installation fails ( even if it seems to work ). COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE ANXIDNST.MSG PROBLEM CONCLUSION: The problem has been fixed adding the message ANX7481E: The Source dir is invalid. Please try again inserting the DOS (CC) Client installation diskette. This message is issued every time the NVDMIDOS is invoked from a diskette different from the first DOS CC Client installation diskette of from a source dir that does not contains all the product files. PTRNBR: 2M04113 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: SEND PROC WITH EAS CORRUPTS THE FILE PROBLEM SUMMARY : Send operation from host to node terminates with RC=0, but the target file is different from origin one. This problem has been found using a file with Extended Attributes. The 'garbage' in the target file consist of some characters taken by the EAs. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem of corrupted file at node, appears with the following conditions: * SEND file with Extended Attributes from NvDM to NvDM/2. * The EAs length is bigger than 4096 bytes (4K). In this scenario the NvDM/2 node executes these steps: 1) The Parser and Builder receives the data from NvDM and it returns to the Specific Server a decoded buffer of 4064 bytes. NOTE: The NvDM data are segmented with 4064 length while the NvDM/2 data are segmented with 4096 length (4K). 2) The Specific Server writes these data in a temporary file and it saves the data length written. 3) The Parser and Builder is called again to decode the remaining E.A. (the sent file has the Extended Attributes bigger than 4096 bytes). 4) The Specific Server computes the E.A. length to write using its segment length (4K): EA_to_write = 4K - EA_written but it is wrong because the E.A. written are 4064 (not 4K). With this fix the Specific Server computes the segment length correctly, then it can write the E.A. of file correctly. PTRNBR: 2M04114 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDMWCAM FAILS WITH GRP WITH SPECIAL CHARACTERS PROBLEM SUMMARY : In case a group name of a Group to install is a name with not standard characters (range 32-126 in the character set), NVDMWCAM fails with message ANX1771. COMPONENTS CHANGED OR ENHANCED: ANXWWTCM.EXE NVDMWUPD.EXE ANXIDMCF.CNF PROBLEM CONCLUSION: A change of character set was necessary (OEM to ANSI). PTRNBR: 2M04123 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: MESSAGE ANXW5215 MISLEADING TO END USER PROBLEM SUMMARY : By DIALOG, opening a CATALOG entry that links a large change file (up to 2674 files) the message ANXW5215 is prompted advising that at this time only 1224 files were shown in the dialog LISTBOX; the remaining will be shown once exit from current LISTBOX and reiterated on FILES button: it is not true since iterating as above always the same 1224 are shown. Besides, the message should be changed or a new one created to inform better about the limitation that move the above product behavior. COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.MSG ANXEDTMS.HLP PROBLEM CONCLUSION: The text of the message has been changed in this way: ANXW5215 The maximum has been reached for the number of items that can be maintained in the list. The list contains the first '%1' entries of the complete list. Help for ANXW5215 EXPLANATION : Only a limited number of items can be displayed in the listbox. USER RESPONSE: None SYSTEM ACTION: Only a subset of items are displayed in the listbox PTRNBR: 2M04126 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: PMR4656X, ACTIVATE WITH DEVICE A DISABLED FOR BOOT PROBLEM SUMMARY : This PTR has been opened to give a quick solution to the Customer POSTGIRO (PMR 4656X,B180,C846). The purpose is to allow the ACTIVATE also in case there is a diskette inserted in drive A or B. This to support the case for which the drive A: has been disabled, via hardware, for the boot. COMPONENTS CHANGED OR ENHANCED: ANXCAQ4S.EXE (ANXCMCLS.EXE) ANXCAQ4C.EXE(ANXCMCLC.EXE) PROBLEM CONCLUSION: The solution consist of setting an environment variable by adding in the config.sys the statement SET ANXCHECKBOOT=NO, in case the User does not want the check on the drives A and B, prior to attempt an ACTIVATE task on the machine. PTRNBR: 2M04131 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: PMR 5992X B100 C838,HANG AT THE END OF THE INSTALLATION PROBLEM SUMMARY : Assume to install NVDM/2 from images located on an optical disk placed in a server. The Customer successfully installed NVDM/2 in server but problem appears when It tries to install it in a workstation. All workstations have OS/2 2.1, LS 3.0 (Requester OS/2). Problem: when It tries to install from diskette images in workstations he has RANDOMLY found next error: when installation is almost finished (99%) appears a Window list which says <Accessing Files> and then PS hangs. COMPONENTS CHANGED OR ENHANCED: PMBODY.EXE PROBLEM CONCLUSION: The problem is due to a missing initialization of a counter, now fixed. PTRNBR: 2M04133 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: RUNTIME ERROR WHEN USING REFRESH FROM CC DOMAIN WINDOW PROBLEM SUMMARY : When the CC Domain window is started and from View pulldown menu the Refresh item is selected then the following runtime error is displayed: Cannot do modal dialog during recursion. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The Refresh item is now available only when the items have been filled in the CC Domain window. PTRNBR: 2M04139 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: PMR 37X80, RUNTIME ERROR 'SYSTEM PRIMITIVE ERROR' PROBLEM SUMMARY : When almost 400 workstations are defined, and from the CDM Catalog attempt to select an object and from Selected menu attempt to select Install item, then a Runtime error 'System primitive error' is displayed. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: When we call API to have a list of WS then we collect all the information written in the reserved memory in a list, using the WS request block for each element of the list. The problem was caused by a wrong request block used. PTRNBR: 5000718 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: IBM 3174,085D0001 (or 085D0002) AT 1ST ATTEMPT OF CONNECTION PROBLEM SUMMARY : The following happens: if a connection is established between a 3174 and NVDM/2 and a function is executed, so that a link is active, after inactivating (via cm) such link, another NVDM/2 node submit a request. At this 1st attempt: - the request ends issuing 085D 0002 - the function of that request is not executed - the queue is released. The request needs to be resubmitted in order to be executed. from this 2nd request on, the problem doesn't occur COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: When the Send Manager receives a REMU with SNA sense code 085D0001 or 085D0002 with Retry Action flag = NO, the Send Manager forces the Retry Action flag = YES so the error is considered retrievable. PTRNBR: 5001048 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: UNEXPECTED MESSAGE ANX0644 DURING A SEND TASK PROBLEM SUMMARY: Attempting a CDM SEND resource to HOST when the resource already exists at Host,the function completes unsuccessfully, as expected, both on the Host that on NvDM/2. The problem is that in the message.dat there is the unexpected message ANX0644: . The Transmission Controller encountered an error on an APPC verb: Verb Name = RECEIVE AND WAIT, Partner LU = xxx, Mode = xxx, and APPC return code = 000E 00000000 COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: When in a distribution, a node issues a SEND_ERROR verb while it is in the receive status, a RECEIVE_AND_WAIT verb returns at the partner node with ret code different from 0, then the ANX0644 message is issued. But before this message, the node issues the message ANX0735 (the node received a REMU) more useful for user. For this reason the message ANX0644 for RECEIVE AND WAIT verb can be not issued. PTRNBR: 5001119 APARNBR: PJ14210 PTFNBR: XR20354 EXTERNAL SYMPTOM: INCORRECT EXECUTION OF AN INSTALL CYCLE PROBLEM SUMMARY : Assuming the following sequence of tasks: - Creating two packages that contain empty directories too such as: AAA.TRIAL.1.REF.1.0 AAA.TRIAL.1.REF.2.0 - Invoking the commands: 1) Install AAA.TRIAL.1.REF.1.0 (desired status INRU, not removable) 2) Install AAA.TRIAL.1.REF.2.0 /R:Y (desired status IRU) . At this time, the AAA.TRIAL.1.REF.1.0 object changes its Status from INRU to BKL. . 3) Remove AAA.TRIAL.1.REF.2.0 object selecting also the 'Restore backup to service area' option . At this time, the AAA.TRIAL.1.REF.1.0 object reverts to INRU Status, while AAA.TRIAL.1.REF.2.0 object changes its Status from IRU to RAR and a SERVICE area directory, for example C:«LT0094A0.SRV, empty directory is created. . 4) Issue an ACTIVATE . At this time,the function ends unsuccessfully despite of the messages logged into the message.dat as follows: . ** NetView DM/2 logged at 17:08:16 19/04/1994 ** ANX1398: (I) CM Activity started. ************************************************* ** NetView DM/2 logged at 17:10:05 19/04/1994 ** ANX1399: (I) CM Activity ended. ************************************************* ** NetView DM/2 logged at 17:10:25 19/04/1994 ** ANX0081: (E) The ACTIVATE request on workstation 'LT0094A0' was unsuccessful due to errors. ************************************************* ** NetView DM/2 logged at 17:10:04 19/04/1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPU2. Return codes were: Primary=20, Secondary=0, Auxiliary=1. Additional Data : 41 4e 58 41 43 50 55 32 30 30 30 31 41 4e 58 43 ANXACPU20001ANXC 43 43 4d 44 43 72 65 61 74 65 20 53 75 62 64 69 CCMDCreate Subdi 72 20 20 20 14 00 00 00 01 00 r ...... COMPONENTS CHANGED OR ENHANCED: ANXACTVD.DLL ANXACTVF.SYS ANXACTVF.EXE ANXCKPUQ.DLL ANXCAQ4C.EXE (ANXCMCLC.EXE) ANXCAQ4S.EXE (ANXCMCLS.EXE FOR Q4 AND Q2 ENVIRONMENT) ANXCAQ3S.EXE (ANXCMCLS.EXE FOR Q3 ENVIRONMENT) PROBLEM CONCLUSION: The problem was due to incorrect management to remove directories from SERVICE AREA. The problem was latent and came up with ACL support. The Pack/Unpack and CDM Agent has been changed to allow now the removing in service area of directory. PTRNBR: 2M04036 APARNBR: PJ08403 PTFNBR: XR20354 EXTERNAL SYMPTOM: DOSCALL1.DLL TRAP D WITH LOGOPTION=COMM CLOSING CM2 1.0 PROBLEM SUMMARY : If NVDM/2 is configured for host focal point connectivity and its logging option is set to CM/2, then if CM/2 is stopped while NVDM/2 is still active, the system will either hang, or a SYS3175 will occur in one of the following modules: - OS2CHAR.DLL - DOSCALL1.DLL - QUECALLS.DLL If NVDM/2 is configured to log to its own log file, then the problem does not occur. The most common of these traps is the one in DOSCALL1.DLL, therefore there is a suspect that the others may be secondary problems. The details of the DOSCALL1 trap are as follows: SYS3175 A program caused an access violation at 1A05272E DOSCALL1.DLL 0005:0000272E P1=00000008 P2=00006E6C P3=xxxxxxxx P4=xxxxxxxx EAX=00000000 EBX=000016D0 ECX 00000027 EDX=0000D067 ESI=00000000 EDI=00000000 DS=D0BF DSACC=00F3 DSLIM=00000077 ES=D03F ESACC=00F3 ESLIM=00001B3F FS=150B FSACC=00F3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=D02F:0000272E CSACC=00DF CSLIM=000054CF SS:ESP=018F:00004486 SSACC=00F3 SSLIM=00005FFF EBP=00006163 FLG=0012286 COMPONENTS CHANGED OR ENHANCED: ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The trap was caused by ANXCMSRV tid 3 that was restarted while its stack was messed up. Tid 9 was the culprit of this stack corruption. In fact, when the CM/2 is stopped, tid 9 tried to log some error messages using Comm Mgr and this operation eated a big amout of stack,even more than the one that was allocated for it. An increase of stack size for tid 9 (NetbiosThread) has been put in place. The stack size has been changed from 2K to 16K. PTRNBR: 2M03979 APARNBR: PJ11737 PTFNBR: XR20354 PROBLEM ABSTRACT: UNRECOVERABLE ERROR DURING ACTIVATE REQUEST. PROBLEM DESCRIPTION: During an ACTIVATE request the following error was logged: ** NetView DM/2 logged at 02:00:06 (AM) 11-19-1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXCCPUM. Additional Data : 41 4e 58 43 43 50 55 4d 30 30 30 34 88 01 00 08 ANXCCPUM0004.... 41 4e 58 43 53 30 46 42 41 4e 58 43 43 50 55 4d ANXCS0FBANXCCPUM 41 4e 58 43 53 50 46 45 10 00 0c 00 20 00 60 05 ANXCSPFE.... .`. 87 95 c4 97 47 00 00 00 00 00 00 00 00 00 00 00 «..-G........... .........00's 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 ................ 04 00 02 00 01 00 01 00 01 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 0f 00 a8 16 00 00 a8 16 00 00 00 00 ......-...-..... a8 16 27 98 f5 04 00 00 00 00 00 00 00 00 00 00 -.'--........... 00 00 00 00 .... COMPONENTS CHANGED OR ENHANCED: ANXCAQ4C.EXE (ANXCMCLC.EXE) ANXCAPMC.EXE (ANXCMCLP.EXE) ANXCAQ4S.EXE (ANXCMCLS.EXE) ANXCAQ3S.EXE (ANXCMCLS.EXE) PROBLEM CONCLUSION: The problem occurred when an external procedure issued a SQLEKILL command that killed the CDM Agent and inherit the handle of the file IBMNVDM2.ALS. The CDM Agent at restart is able to open the file but when the activate is processed the file is closed and the following copy operation ends with OS/2 RC=32 because the file result still owned by DB/2. The problem was bypassed developing a new function that allow to copy the IBMNVDM2.ALS in IBMNVDM2.SAV without closing the file. PTRNBR: 2M03987 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: IPL FAILS IF CONFIG.SYS FILE ENDS WITHOUT CRLF PROBLEM SUMMARY : CC Server or CC Client fail at IPL due to NvDM/2 related DEVICE statement joined, within CONFIG.SYS, with another on the same line that cannot be processed. COMPONENTS CHANGED OR ENHANCED: BODY.EXE SBODY.EXE PMBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION: The failing event was due to missing CRLF in the CONFIG.SYS, as per a previous edit task, that caused the write, at product installation time, of the DEVICE=........ statement to be joined instead of appended to the last line of the CONFIG.SYS. Now, the NvDM/2 installation programs manage also this condition. PTRNBR: 2M04017 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: RETRIEVE TASK FAILS OR LOOP AT TARGET NODE IF LOCAL SEND PROBLEM SUMMARY : RETRIEVE function fails at host because of a wrong number of bytes was received from remote node. If the same resource is sent from/to NvDM/2 nodes,this results as a loop at the target code due to a lot of FSTxxxxx files creation in the FSDATA directory. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: Fixed a limit condition when preparing a resource to send. PTRNBR: 2M04020 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: ACTIVATE,FILES NOT MOVED WITH PARTICULAR CONFIG.SYS PROBLEM SUMMARY : Assuming a config.sys with 'DEVICE' statements before the IFS statement. When the ACTIVATE function is issued the files are not moved from the service to the active area. Moreover, even if the files are not moved, the message of ACTIVATE successfully executed is stored in the message.dat whatever configured. COMPONENTS CHANGED OR ENHANCED: ANXCAPMC.EXE (ANXCMCLP.EXE) ANXCAQ3S.EXE (ANXCMCLS.EXE) ANXCAQ4C.EXE (ANXCMCLC.EXE) ANXCAQ4S.EXE (ANXCMCLS.EXE) PROBLEM CONCLUSION: The problem occurred because of the logic,used by NVDM/2 in inserting the DEVICE statement for ANXACTVF.SYS and the RUN statement for the ANXACTVF.EXE procedure. In fact they above statewment were placed after the first encountered IFS statement or before the first encountered DEVICE statement. Moreover no error message was logged because of the not loaded File System. The problem has been solved by changing NvDM/2 logic in the way that the two statements are added after the first encountered IFS statement (if it is not the NVDM2 IFS statement). If an IFS statement does not exist or the only IFS statement is that NVDM/2 one (ANXIFCOM.IFS) the two statements are added on top of the CONFIG.SYS. OM. PTRNBR: 2M04023 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDMBDSK DOES NOT WORK TO CREATE BOOT DISKETTES BECAUSE OF NETVIEW DM/2 BOOT DISKETTE CODE EXCEED 100K SIZE PROBLEM SUMMARY : Since DBCS Support (XR20334 CSD) the NetView DM/2 code on the boot diskette is increased up to about 210Kbyte. COMPONENTS CHANGED OR ENHANCED: ANXPULAG.EXE NDMNLSP.DLL PROBLEM CONCLUSION: Now the Boot diskette code is again under the 100Kbyte. PTRNBR: 2M04033 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: COMMAND LINE, 'SIGNAL' RC MUST BE IGNORED PROBLEM SUMMARY : Command line cannot be issued by a PM program because it terminates with ANX0211. The is because 'signal' function returned with -1 and command line interprets it as an error. COMPONENTS CHANGED OR ENHANCED: CDM.EXE PROBLEM CONCLUSION: The command line goes on with processing if it cannot ignore the CTRL-C signal. PTRNBR: 2M04038 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: INSTALL DOESN'T MANAGE ERRORS ON MORE WS IN A LIST PROBLEM SUMMARY : Running a CDM INSTALL of a co-requisite groups with a workstation list with more than one workstation and some of the objects had an invalid status,the installation failed only for the first workstation. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Problem fixed in both CDM Command line and Dialogs. PTRNBR: 2M04040 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDMBDSK FAILS WITH MIXED CASE NETBIOS DRIVERS STATEMENTS. PROBLEM SUMMARY : NVDMBDSK at XR20334 fails to find NetBIOS support on a DOS client startup diskette if the DXM drivers are entered in lowercase or in mixed case in the CONFIG.SYS. In fact if the prefix device is not written as DEVICE= or the device specifications are not written with the 3 first letters DXM in uppercase, NVDMBDSK answers stating that netbios is not installed on the target startup diskette COMPONENTS CHANGED OR ENHANCED: NVDMBDSK.EXE PROBLEM CONCLUSION: The problem was due to a case sensitive check done on the CONFIG.SYS, now fixed. PTRNBR: 2M04043 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: RESOURCE GLOBAL NAME 10TH TOKEN NOT DISPLAYED IN MESSAGE.DAT PROBLEM SUMMARY : If the user catalogs an object as SOFTWARE or FLATDATA with a Global Name with 10 token, any time he tries to do a CM operation with this object, It finds that the messages related to this operation have recorded the Global Name with the 10th token lost or damaged. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: A wrong message management was recognized in the message handler, now fixed. PTRNBR: 2M04046 APARNBR: PJ11806 PTFNBR: XR20354 EXTERNAL SYMPTOM: EA FILES TIMESTAMP CHANGED AFTER INSTALL FOR HPFS386 PROBLEM SUMMARY : If an INSTALL operation is executed (doesn't matter if on service or active area) in a machine running HPFS386 file system running (ie having the Lan Server 3.0 installed) the timestamp, for the files involved in this action, is changed into the current one. This occurrence is due to the way the HPFS386 manages the EAs files. In fact when this file system accesses the EAs files, it changes the timestamp into the current one. The effect of this behaviour is that, if we check the result of an INSTALL operation in the target dir (it may be in the active or in the service area) we find that the date for the files was changed and it was different from that had the source files when the CDM change file was created. COMPONENTS CHANGED OR ENHANCED: ANXCKCLI.DLL ANXCKPUQ.DLL ANXCKSRV.DLL PROBLEM CONCLUSION: The problems has been resolved changing the setting order, first EA and then the file info. PTRNBR: 2M04014 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: SPECIAL CHARACTERS NOT SUPPORTED PROBLEM SUMMARY : The special characters NUMBER SIGN and AT SIGN were not recognized as valid for global names. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Now, the special characters allowed in a global names are: at-sign,num-sign,dollar (as stated from SNA/FS architecture) and '_', underscore. PTRNBR: 2M04032 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: INITIATE,MULTIPLE OCCURRENCE MAY CAUSE SYS ABEND 3 PROBLEM SUMMARY : A Customer experienced that multiple occurrence of a plan that submitts the same INITIATE task, could cause, if the workstation is not switching off for several days, the Change Controller to end because of system abend 3. From that point in time on, every time It initiates the procedure, the Change Controller abends. If It uncatalogs the PROCEDURE and recatalogs it again, NetView DM/2 restart to work fine. COMPONENTS CHANGED OR ENHANCED: ANXSAQ4S.EXE (ANXCMSRV.EXE FOR Q4 ENVIRONMENT) ANXSAQ3S.EXE (ANXCMSRV.EXE FOR Q3 ENVIRONMENT) ANXSAQ2S.EXE (ANXCMSRV.EXE FOR Q2 ENVIRONMENT) PROBLEM CONCLUSION: The problem was due to an undesired limit,now removed,of occurrences of the same procedure. PTRNBR: 2M04050 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: A SECONDARY EFFECT CAUSES CHANGE CONTROLLER TO END PROBLEM SUMMARY : Any change management task that apply to the same global name (i.e.,INSTALL,REMOVE,etc.) causes the NvDM/2 V2 at XR20334 to fail. The problem appears when sending a report to NvDM Focal Point; if unsolicited report was set to NO the problem does not appear. NOTE: A secondary effect means those entries with the same component name of an already installed entry. Hereafter a sample of the errors and messages that are logged when the failing event takes place. MESSAGE LOGS ============ The following sequence if messages could be experienced if the failing event takes place during an INSTALL task,with UnSolicitedReports=YES, that is supposed to install a resource such TEST.TEST.REF.02 over an existing TEST.TEST.REF.01 one. ** NetView DM/2 logged at 08:18:11 (AM) 02-09-1994 ** ANX0057: (I) The INSTALL request for an object with Global Name 'TEST.TEST.REF.02' on workstation 'ROMELU00' was successful. ** NetView DM/2 logged at 08:19:49 (AM) 02-09-1994 ** ANX0211: (E) An unrecoverable error prevents continuation of processing. ** NetView DM/2 logged at 08:21:16 (AM) 02-09-1994 ** ANX0074: (E) The Change Controller ended because of errors. These messages indicate that the INSTALL was successful, and a CDM LIST command confirms this (ie, the history for TEST.TEST.REF.01 was removed, and TEST.TEST.REF.02 was INRU) ERRORS LOGS =========== ** NetView DM/2 logged at 15:02:36 11/01/1994 ** Error detected in NetView DM/2 DS component. The error was generated in module . Additional Data : 8b 45 0c 89 45 f8 8b 40 30 30 30 34 34 00 00 08 .E. E-.@00044... 41 4e 58 43 53 30 4d 42 00 00 00 00 00 00 00 00 ANXCS0MB........ 41 4e 58 43 53 50 4d 33 10 00 0c 00 05 00 00 00 ANXCSPM3........ ** NetView DM/2 logged at 15:02:53 11/01/1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXAFPEA. Return codes were: Primary=8, Secondary=8, Auxiliary=0. Additional Data : 41 4e 58 41 46 50 45 41 30 30 30 31 41 4e 58 43 ANXAFPEA0001ANXC 52 50 47 43 00 00 00 00 00 00 00 00 00 00 00 00 RPGC............ ** NetView DM/2 logged at 15:02:55 11/01/1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPMT. Additional Data : 41 4e 58 41 43 50 4d 54 30 30 30 34 34 00 00 08 ANXACPMT00044... 41 4e 58 43 53 30 4d 42 41 4e 58 41 43 50 4d 54 ANXCS0MBANXACPMT 41 4e 58 43 53 50 4d 33 10 00 0c 00 05 00 00 00 ANXCSPM3........ COMPONENTS CHANGED OR ENHANCED: ANXLCPB.DLL PROBLEM CONCLUSION: The above failing scenario was due to a latent wrong, now fixed, handling of the memory reserved to CM messages. PTRNBR: 2M04054 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: '¹' (AT SIGN) CHARACTER NOT ALLOWED ON LU NAME PROBLEM SUMMARY : Using the 'at-sign' character as first character of the LU Alias in a connection Id when defining Remote Destinations, the result was either error ANXE5101 RC=0 Reason=11 via Dialog or ANX0211 via Command Line. This is because ES 1.0 and CM/2 do not allow at-sign as first character in a LU alias. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: By Dialogs,if specify 'at-sign' character is specified as first character of a LU alias, the Define Remote destination now fails with message ANXE5407 instead of ANXE5101 one. The ANXE5407 message advices that a not allowed character was typed in either LU Alias or Mode fields. By command line, the companion message that advices that a not allowed character has been typed for LU Alias is ANX360E. PTRNBR: 2M04058 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: DOS CLIENT HANG IN INSTALLING A PC3270 PACKAGE PROBLEM SUMMARY : Installing a package formed by 199 files belonging to the PC3270 directory, an hang of the cc DOS client happens. The hang happens after having unpacked all the files and before the final reboot in order to give back the controll to the user. No action is possible other than power off the machine. After the machine is up again the install process is completed without any other problem. At the moment in which the client hangs, on the server both .CLI and .END file are present in the directory <product_dir>«CMREQ«<client_name>. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE ANXCMEXE.EXE PROBLEM CONCLUSION: The hang was fixed using a new compilation option when building the product code. PTRNBR: 2M04059 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: CDM ACTIVATE DOES NOT WORK WITH READ ONLY CONFIG.SYS PROBLEM SUMMARY : When CONFIG.SYS has the attribute READ_ONLY, the ACTIVATE task fails while the CDM Agent end because of error. Hereafter the error record logged into error.dat file: ** NetView DM/2 logged at 14.31.14 25-01-1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACCWC. Return codes were: Primary=20, Secondary=0, Auxiliary=5. Additional Data : 41 4e 58 41 43 43 57 43 30 30 30 31 44 6f 73 43 ANXACCWC0001DosC 61 6c 6c 73 44 6f 73 43 6f 70 79 00 00 00 00 00 allsDosCopy..... COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE ANXACTVF.EXE PROBLEM CONCLUSION: The ACTIVATE works making a temporary config.sys upon which it builds activate modifications. Once the config modification is ended it copies the temporary config overriding the real one. The process has made by a DosCopy without any check on the target config.sys; in case this has read only attribute, the DosCopy failed. Now a check is introduced. In case the Config is read only, the attribute is temporarly removed, the DosCopy is performed and then the READ ONLY attiribute is set on again. PTRNBR: 2M04060 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: 090 COUTRY CODE NOT SUPPORTED BY NVDM2 PROBLEM SUMMARY : If a Turkish operation system is installed and in the config.sys the country code field is set to 090,NvDM2 is not able to start. In fact, when invoking a CDM START from command line the following message is prompted: 'The command is in progress. Check Transmission Controller status later'. Then, the message 'ANX0181 Transmission is not active'. is prompted. Using CDM DIALOG and clicking the mouse button to activate CDM MANAGER now get 'ANXI5703,Transmission Controller is in process of being started' and then get 'ANXE5101 RC=0,Reason=6013'. Hereafter an abstract for the error.dat tha is logged: . Error detected in NetView DM/2 CM component. The error was generated in module ANXBIP01. Additional Data : 41 4e 58 42 49 50 30 31 30 30 30 34 88 05 00 08 ANXBIP010004.... 41 4e 58 43 52 30 47 42 41 4e 58 42 49 50 30 31 ANXCR0GBANXBIP01 41 4e 58 43 52 50 47 32 10 00 14 00 00 00 00 00 ANXCRPG2........ 00 00 00 00 0a 14 20 20 00 00 00 00 00 00 00 00 ...... ........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: The country code 090 is now supported. PTRNBR: 2M04026 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: COMMAMD LINE,/WS IMPLICITELY LIMITS TO HAVE 255 PWS PROBLEM SUMMARY : All commands have an implicit limit to manage 255 WS when /WS without is specified without an argument. COMPONENTS CHANGED OR ENHANCED: CDMSRV.EXE (as CDM.EXE on CC Server or CDM Base) PROBLEM CONCLUSION: Command line manages up to 1000 workstations when using the /WS parameter without argument. If the argument is a list file, then the workstations in the list can be only 255. PTRNBR: 2M04047 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: CORRUPTED TXT FILE WHEN COMPRESSED WITH NVDMLZW. PROBLEM SUMMARY : Assuming to attempt a SEND of a TXT file with NVDMLZW compress algorithm. The SEND operation ends successfully but the file at the target site is different from the origin file. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The problem occurs when the NvDM/2 node sends a TXT file. This file is bigger than 64K bytes and it is sent compressed with NVDMLZW algorithm. With this condition the Transform Handle is called to perform the file transform operation. The problem is found in TXT file handling, when a MEMCPY function is called with wrong parameters sequence. This bug was the cause of wrong txt output file. PTRNBR: 2M04053 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: INSTALLATION FAILS DUE TO DEVICE STATEMENT MISPLACED IN CONFIG.SYS PROBLEM SUMMARY : At the product installation time, the statement such as DEVICE=ANXACTVF.SYS misplaced before the IFS=.... one causing the product installation to fail when moving file from temporary to target area. COMPONENTS CHANGED OR ENHANCED: ANXIISNA.EXE BODY.EXE NVDMBDSK.EXE NVDMEPMS.EXE NVDMPMS.EXe PMBODY.EXE PMSBODY.EXE SBODY.EXE PROBLEM CONCLUSION: Now, the DEVICE is placed according to the workstation configuration (i.e., just after the IFS that installs the HPFS386 or just before the first DEVICE=... statement if standard HPFS or FAT file system was chosen). PTRNBR: 2M04065 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: DISK CAMERA DOES NOT WORK PROPERLY WITH NOT USA WINDOWS PROBLEM SUMMARY : Assuming the following scenario: trying to run NVDMWCAM for PC/3270 3.1 Windows version, the PC/3270 installation completed normally and NVDMWCAM started comparing files. When it came to 'DiskCamera is comparing the file:PROGMAN.INI', it hanged. This happens using DOS 6.1 and a not-USA Windows 3.1 on a P70. After re-booting,checking NVDMUPD.MOD,the last two lines were: PROGMAN.INI CreateGroup(PC/3270) COMPONENTS CHANGED OR ENHANCED: NVDMWCAM.EXE PROBLEM CONCLUSION: The problem was due to the reference point ('Program Manager') used by NVDMWCAM that it is valid only for US Windows version. Now, the reference point has been changed to comply with both US and not US Windows versions. PTRNBR: 2M04066 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: DIALOG,TIMEZONE NOT RETRIVED CORRECTLY BY ANXEDINI PROBLEM SUMMARY : A Customer, running at NVDM/2 V2 XR20334 (XR00005) December 1993 level, is experiencing that ANXEDINI does not retrieve the TIMEZONE value,even correctly set, either from IBMNVDM2.IN I file and OS/2 Operating System: it presents always 0. In particular, the Customer experienced that having changed the TIMEZONE value,from 0 to a certain value, and having assessed that this was written correctly to IBMNVDM2.INI, just invoking TYPE IBMNVDM2.INI, the TIMEZONE value presented anytime later is always 0 even having stopped and restarted NvDM/2 V2. More, verifying the Customer occurrence at Lab, we assessed that the changed TIMEZONE value, even not retrieved correctly by ANXEDINI,was either correctly changed into the IBMNVDM2.INI file and initialized at product start up. COMPONENTS CHANGED OR ENHANCED: ANXEDINI.EXE PROBLEM CONCLUSION: The problem was due to a wrong management of the entry field TimeZone, now fixed. PTRNBR: 2M04071 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: INCORRECT ERROR MESSAGE ANX1727 PROBLEM SUMMARY : An incorrect Error message, <ANX1727(E),Cannot execute internal module.>, was displayed when the name of installation product is wrong. For example, invoking NVDMWCAM Product /N:PRODUCT where 'Product' is a wrong name of an installation product, the message prompted should be: - ANX1731(E) The user application <Product> cannot be found or executed COMPONENTS CHANGED OR ENHANCED: NVDMWCAM.EXE NVDMWUPD.EXE PROBLEM CONCLUSION: Now, when the End User types a wrong name about the installation product, the following message is prompted: - ANX1731(E) The user application <Product> cannot be found or executed. PTRNBR: 2M04072 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: CD-ROM IS NOT ACCEPTED FOR BUILD COMMAND PROBLEM SUMMARY : The cdm BUILD fails with unrecoverable error if the source files are on a CD-ROM disk. The related error log is the following: 41 4e 58 45 46 43 4c 4e 30 30 30 34 88 05 00 08 ANXEFCLN0004.... 41 4e 58 43 52 30 47 42 41 4e 58 45 46 43 4c 4e ANXCR0GBANXEFCLN 41 4e 58 43 52 50 47 45 10 00 0c 00 05 00 00 00 ANXCRPGE........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: The problem was due to wrong mode used when accessing CD-ROM, now fixed. PTRNBR: 2M04073 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: ANX0245 DECIMAL NETBIOS RC INSERTED WITH HEXADECIMAL FLAG PROBLEM SUMMARY : When error message ANX0245 (Unexpected error occurred interfacing NetBios. return code 'rc'X) is stored in message.dat file, the NetBios return code is inserted with its decimal value in spite of the hexadecimal flag 'rc'X. Customer highlighted this item as misleading for analysis and requests it to be fixed. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL ANXPULAG.EXE ANXCAPMC.EXE PROBLEM CONCLUSION: The return code (rc) is now set as hexadecimal. PTRNBR: 2M04075 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: EMPTY DIRECTORIES ARE DELETED WHEN REMOVING OBJECTS. PROBLEM SUMMARY : Installing removable a package, the back level empty directories are not recorded in the back level package. Thus if both the old and the new version of the package have some empty directory and a remove is asked to go back to the old level,NVDM2 delete the empty directory of the new level but does not create again the empty directory for the old one. This behavior cause some product to fail because they need these directories. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: Now,the Back level empty directories are not deleted anymore. PTRNBR: 2M04079 APARNBR: PJ12175 PTFNBR: XR20354 EXTERNAL SYMPTOM: INITIATE FAILS ON DOS CLIENT IF PROC IS NOT A .BAT PROBLEM SUMMARY : Executing a Send Initiate from Host, the procedure is stored on the server as FSFxxxxx without any extension. Running the initiate at the client the Dos Client fails stating that the procedure cannot be used in DOS mode COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: The problem is due to missing management of an initiate of a procedure that was arrived throw a remote command. Now, the appropriate management has been inserted. PTRNBR: 2M03795 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: ANXRXINI.EXE, ANXVDSK.EXE AND ANXDELD.EXE NEITHER INSTALLED OR UPLOADED PROBLEM SUMMARY : The NvDM/2 V2 refreshed by December 1993 or upgraded with CSD XR20334 does not install or upload the following files referenced into GG66-3253-00: a - ANXVDSK.EXE b - ANXDELD.EXE c - ANXRXINI.EXE COMPONENTS CHANGED OR ENHANCED: ANX1.TXT ANX1E.TXT ANXCOPY1.TXT ANXCPY1E.TXT ANXF.TXT ANXFE.TXT ANXFPM.TXT BNX1.TXT BNXCOPY1.TXT BNXCP1PM.TXT PROBLEM CONCLUSION: Now, the above files are both correctly installed by this CSD and managed by NvDM/2 V2 related installation programs when reinstalling from product images upgraded at XR20354. PTRNBR: 2M04068 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: HANG IN APPC ALLOCATE REQUEST PROBLEM SUMMARY : If a polling request is received by the node while the node is trying to send a request, an hang occurs between the two requests (allocate and receive_allocate). COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: Transmission controller hangs when its scheduler must process a remote ReceiveAllocate Appc verb (polling from partner) and it must also process a local Allocate APPC verb to send a resource to the same partner LU. The problem happens in the following scenario: The Scheduler has in its queue a Send data request and a Receive Allocate request. The Scheduler performs in sequence this two steps: 1) Process Send data: a) Start Send Manager thread b) set ACB.NOSINST=1 (Number of active Send Manager Threads) 2) Process Receive Allocate: a) If ACB.NOSINST=0 then it starts a Send Manager The hang problem happens when the Receive Allocate is processed before that Send Manager thread terminates to work (ACB.NOSINST value remains equal 1). The Allocate requested from Send Manager doesn't return to the caller because the Receive Allocate is allocating that session. Now, when the Receive Allocate process is starting, the Scheduler tests the ACB.NOSINST value. If ACB.NOSINST = 1 then the Scheduler deallocates the conversation required from Receive Allocate (polling request). That conversation will be allocated from Send Manager thread. PTRNBR: 2M04069 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: NVDM/2 DOESN'T WORK ON ALL DOS V6.X PROBLEM SUMMARY : Using NvDM/2, CSD XR20334, over DOS 6.3 there were problems originating the following ERROR.DAT and MESSAGE.DAT and causing never ending reboot on DOS machines. . ERROR.DAT ========= ** NetView DM/2 logged at 11:35:57 (AM) 02-10-1994 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXCCCSR. Return codes were: Primary=20, Secondary=0, Auxiliary=101. Additional Data : 41 4e 58 43 43 43 53 52 30 30 30 31 41 4e 58 43 ANXCCCSR0001ANXC 43 43 53 52 20 20 20 20 20 20 20 20 00 00 00 00 CCSR .... 00 00 00 00 14 00 00 00 65 00 49 66 73 53 74 61 ........e.IfsSta 72 74 52 65 71 00 00 00 00 00 00 00 00 00 00 00 rtReq........... . MESSAGE.DAT =========== ** NetView DM/2 logged at 11:35:46 (AM) 02-10-1994 ** ANX0241: (E) Unexpected error interfacing the Redirector. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE ANXCMEXE.EXE ANXCAPMC.EXE PROBLEM CONCLUSION: This problem was due not announced DOS version that was not handled. Now,a check on DOS version has been modified in order to prevent rc=101 (UNSUPPORTED DOS VERSION) from IfsStartReq. PTRNBR: 2M04070 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: PERFORMANCE,PROBLEMS USING 6611 ROUTERS PROBLEM SUMMARY : Using NvDM/2, over a WAN where 6611 routers are involved, the INSTALL tasks were too long, especially if compared with some performed using Lan Server product. COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.DLL ANXIFREQ.DLL ANXIFSRV.EXE ANXIFPID.SYS ANXIFCOM.SYS ANXIFCOM.IFS PROBLEM CONCLUSION: Several changes have been done in the communication protocol so now we can save a lot of time when using our product on big LAN-WAN. We also reduced dramatically the amount of data sent through the LAN-WAN. Moreover on DOS side now it is possible to use PBA values different from 0 while before this fix PBA not equal 0 meant bad performances. On OS/2 side, the related clients had one more command. More exactly we need the double of the number of commands previously used and as this value is 1 we need 1 more cmd. This fix is compatible with the past but to maintain compatibility with a previously existing environment we have FIRST to install the server and ONLY AFTER THIS,to install or to upgrade the clients: THIS IS VERY IMPORTANT|| ======================== More exactly, the End User should be aware that only the following scenarios could be run: Server New <----------------------> Client New (DOS and OS/2) Server New <----------------------> Client Old (DOS and OS/2) Server Old <----------------------> Client Old (DOS and OS/2) . WHILE IT IS NOT POSSIBLE TO RUN =============================== . Server Old <----------------------> Client New (DOS and OS/2) WHERE Old means CSD XR20334 and New means CSD XR20354, this CSD. PTRNBR: 2M04084 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRAP WHEN INSTALLING COREQUISITES ON HOST_ATTACHED ENVIRONEMNT PROBLEM SUMMARY : Executing an install of some packages as a group of co-requisites on an entry machine, a sytem abend 2 happens. Herafter the related TRAP D information that are different from 0: ANXCMSRV 0006:00048da9 DS=009f DSACC=00f3 DSLIM=0000d257 FS=850b FSACC=00f2 FSLIM=00000030 CS:EIP=0027:00008da9 CSACC=00fb CSLIM=0000fd29 SS:ESP=01d7:0000947e SSACC=00f3 SSLIM=0000fa5f EBP=0000b110 FLG=00012246 COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The problem was due to wrong management of the corequisite list, now fixed. PTRNBR: 2M04085 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRAP IN ANXCKPUQ.DLL IF A CHANGE FILE HAS NOT FILES OR EMPTY DIRs PROBLEM SUMMARY : A trap occur trying to install a chenge file with no file packed or only empty Directories are present. Hereafter the TRAP information: SYS3175 ANXCKPUQ.DLL 0005: 011d10c0 A program encountered an access violation at 011d10c0 P1=00000000 P2=ffffffff P3=xxxxxxxx P4=xxxxxxxx EAX=00000100 EBX=0000ffff ECX=00000004 EDX=00000c17 ESI=0000f3e8 EDI=00000000 EBP=0000f3c6 FLG=00012212 DS=009f DSACC=00f3 DSLIM=0000ffff ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=ce17:000015ca CSACC=00fb CSLIM=000038f7 SS:ESP=009f:0000f3c0 SSACC=00f3 SSLIM=0000ffff COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: In case of no files are present in the change file the ListBuffer pointer was not initialized and its usage caused the TRAP. Now, a flag for the presence of any file has been added. In case only empty directories are present the List Buffer pointer is not used any more. PTRNBR: 2M04087 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: DOS PRISTINE DELETE NEEDED COMMAND.COM IF IN ERROR PROBLEM SUMMARY : If an external install fails for some reason, like for example an external command not found, the DOS Pristine machine deletes the needed copy of COMMAND.COM in the ANXDPRST«BIN« directory on the boot diskette. This action causes the diskette not to work with batch files that needs the above mentioned COMMAND.COM copy in order to be executed. The deletetion is due to a misfunctioning ANXCMBOT.EXE module. COMPONENTS CHANGED OR ENHANCED: ANXCMBOT.EXE PROBLEM CONCLUSION: The problem occured because of a wrong check in the anxcmbot program. PTRNBR: 2M04090 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: UNRECOVERABLE ERROR IN REMOVE IF SRVNAME IS CHANGED. PROBLEM SUMMARY : The agent fails with ANX0074:(the agent ended because of errors) when,after an install,the SRVNAME is changed (by the Comm. Mgr) and a Remove (or an Accept) is issued. The failing scenario is below described: a - Install a change file REMOVABLY,which takes a backup of existing files. b - Modify LU name in NDF file Verify NDF file c - Stop NvDM/2 d - Stop CM e - Restart CM f - Restart NvDM/2 g - Verify that the server name is changed issuing CDM LISTWS h - Invoking CDM ACCEPT or REMOVE of above change files results in Agent ends in error. . Hereafter the related ERROR log: . 41 4e 58 41 43 50 42 44 30 30 30 31 41 4e 58 43 ANXACPBD0001ANXC 53 43 44 32 53 45 41 52 43 48 20 46 53 20 43 41 SCD2SEARCH FS CA 54 20 20 20 08 00 08 00 64 00 20 20 20 20 20 20 T ....d. ........ 20's 20 20 20 20 20 20 20 20 20 20 20 20 20 20 94 06 00 08 41 4e 58 43 53 30 44 42 41 4e 58 41 43 50 ..ANXCS0DBANXACP 42 44 00 00 00 00 00 00 00 00 08 00 08 00 64 00 BD............d. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 08 00 4b 4c 4f 4e 44 49 4b 45 20 20 ......KLONDIKE 20 20 20 20 20 20 54 45 53 54 20 20 20 20 20 20 TEST 20 20 20 20 20 20 52 45 46 20 20 20 20 20 20 20 REF 20 20 20 20 20 20 31 20 20 20 20 20 20 20 20 20 1 ........ 20's COMPONENTS CHANGED OR ENHANCED: ANXSAQ4S.EXE (ANXCMSRV.EXE FOR Q4 ENVIRONMENT) ANXSAQ3S.EXE (ANXCMSRV.EXE FOR Q3 ENVIRONMENT) ANXSAQ2S.EXE (ANXCMSRV.EXE FOR Q2 ENVIRONMENT) PROBLEM CONCLUSION: The problem was due to SRVNAME not updated in the catalog, now fixed while attempting to perform REMOVE or ACCEPT task. PTRNBR: 2M04100 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: TRAP C OR HANG WHEN INVOKING CDM TRACE_ON PROBLEM SUMMARY : When running NvDM/2 V2.0,at CSD XR20334 or higher, over OS/2 2.1 + CM/2 + DB2/2 and attempting to invoke CDM TRACE_ON, the following two symptoms are experienced: a - HANGING and no prompt returned; OR b - TRAP C . COMPONENTS CHANGED OR ENHANCED: ANXSNADL.EXE PROBLEM CONCLUSION: The problem was due to insufficient stack of the ANXSNADL executable module, now fixed. PTRNBR: 1000089 APARNBR: PJ13835 PTFNBR: XR20354 EXTERNAL SYMPTOM: LDS SHOULD CLOSE AFTER A TIMEOUT IF NO RECEIVER PROBLEM SUMMARY : At start of LDU Distributor no function has performed until a Receiver is connected at least. Using LDU from the host if there is a failure on the LAN no messages are provided. LDU Distriibutor must stop distribution (with a message in the log) if no receivers were connected within a certain time. COMPONENTS CHANGED OR ENHANCED: LDS.EXE LDSDMSG.MSG PROBLEM CONCLUSION: The TIMEOUT variable has been changed. Now it can be set to two different values separated by a comma. The first is still the lenght of time that Distributors waits for a receiver connection while the second is the max number of cycles that the distributor does to wait the first receiver connection (this was before harcoded as infinite). The second value of the variable has the same range of use as the first. In case a second value is set and no receiver connects, two messages are logged: the first states the number of cycles and the second records that no receiver has been connected. On the other hand, when a distribution starts the message of the number of cycles really executed has been logged in order to help the tuning of the second value of TIMEOUT. Of course a new documentation related with the variable is inserted in README.TXT PTRNBR: 2M04061 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: DIALOG,UNRECOVERABLE ERROR IF USERID NOT AUTHORIZED PROBLEM SUMMARY : Logging on with a not authorized userid and opening the dialog, causes the display of a message about an unrecoverable error. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXEDTMS.MSG ANXEDTMS.HLP PROBLEM CONCLUSION: A message related to the lack of authorization to the database is now displayed when trying to open the dialog when having logged on to the database with a not authorized userid. PTRNBR: 2M04062 APARNBR: PJ11990 PTFNBR: XR20354 EXTERNAL SYMPTOM: DIALOG,OPEN CATALOG OBJECT FAILS IF LINKED WITH LONG LOCAL FILENAME PROBLEM SUMMARY : Opening a CATALOG entry, associated with a local filename long up to 41 characters and composed of 9 tokens, fails with message ANXW5650: The text of the message is: File 'D:\FSDATA\IBM.DB2V10.WR07000.CCSERVER.REF.1.0.0.CHG' does not exist. Of course,the file exists in the FSDATA area. More, in spite of the above mentioned error message, the catalog entry can be deleted or installed. The change file profile used is: TargetDir=C:\ Section Catalog Begin ObjectType = Software GlobalName = ibm.db2v10.wr07000.ccserver.ref.1.0.0 Description = 'DB/2 Ver 1.0 Installation for a CC Server' End Section Install Begin Program = SA:\IMG\DB2V10\DB2SU\DBCID.EXE Parms = /S:$(SourceDir) /R:$(ResponseFile) /L1:$(logfile1) /L2:$(logfile2) SourceDir = SA:\IMG\DB2V10\DB2SU ResponseFile = SA:\RSP\DB2V10\ccserver.rsp Logfile1 = SB:\LOG\DB2V10\$(WORKSTATNAME).L1 Logfile2 = SB:\LOG\DB2V10\$(WorkStatName).L2 End The following is the syntax used to invoke CDM BUILD command: CDM BUILD IBM.DB2V10.WR07000.CCSERVER.REF.1.0.0.PRO FS:IBM.DB2V10.WR07000.CCSERVER.REF.1.0.0.CHG COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: To test the existence of the Local File we call the DosFindFirst; the problem was caused by a buffer overloading. Now,the size of this buffer is changed. PTRNBR: 2M04086 APARNBR: PJ13306 PTFNBR: XR20354 EXTERNAL SYMPTOM: LARGE CHG FILE CAN'T BE OPENED VIA DIALOG (MSG ANXE5603) PROBLEM SUMMARY : When a CHG file is built containing a large number of files, up to 1700 with a range from 1K and 30K in size, attempting to perform the following actions: 1 - Open the Catalog and highlight the entry; 2 - Click on SELECTED; 3 - Click on OPEN; 4 - Click on FILES; the message ANXE5603,<Invalid Change File>,is prompted. By the way, executing,from command line,CDM QUERY_CF of the same resource (change file), the files are correctly listed. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXEDTSN.DLL PROBLEM CONCLUSION: The problem was due to an incorrect handling of large list, now fixed. However, the End User should be aware that even the problem is fixed, only a portion of a large list could viewable in a dialog list box due to machine memory constraints dependency: for a complete list use the CDM QUERY_CF command. PTRNBR: 2M02860 APARNBR: PJ09350 PTFNBR: XR20334 EXTERNAL SYMPTOM: SNA CODE 100B000C DETECTED WITH DISPOSITION=DELETE PROBLEM SUMMARY : Transmission activities between Netview DM V1R3 and Netview DM/2 V2. An Agent exception with SNA Code 100B 000C is detected at the node when submitting and executing a SEND&INITIATE PROCEDURE from the host (the unsupported data value is the Object Disposition that is not specifiable by the user). The same problem occurs if an INSTALL function is executed with Disposition=Delete parameter specified. In order to be congruent with the previous version of the product, the Disposition parameter should be ignored even if not processed and the functions (both the INITIATE and the INSTALL) should complete successfully. COMPONENTS CHANGED OR ENHANCED: ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The current product version should support only the Disposition 'KEEP' for an Initiate or Install operation. The NvDM 1.4 in order to allow this new mode to operate was changed in order to set the Default parameter for an INITIATE operation to blank. Consequently when the request arrives to the node the NvDM/2 resolve this parameter setting it to 'KEEP'. Now there is the need to allow the communication between release 2 of NvDM/2 and NvDM 1.3. The only way to do this is retrofitting the fix NvDM 1.4 on NvDM 1.3. In this mode no problem will happen because the release 2 of NvDM/2 solve this parameter setting it to 'KEEP'. However, following a design meeting, now the NDM 1.3 could not set the parameter DISPOSITion. So, to make the NvDM versions transparent, this value will be solved at the node and if it is a NDM2 REL1 this value will be set to DELETE instead if the node is a NDM2 REL2 it will be KEEP. For an INSTALL operation if the user will set it to DELETe he must aware of the fact that the NDM2 REL2 supports now only THE KEEP VALUE SO THE SENSE CODE DESCRIBED IN THE PROBLEM DESCRIPTION PARAGRAPH WILL RETURN TO THE IOF. PTRNBR: 2M03424 APARNBR: PJ08250 PTFNBR: XR20334 EXTERNAL SYMPTOM: UNKNOWN CONTEXT MENU INTO MESSAGE LOG WINDOW PROBLEM SUMMARY : Unknown context menu appears when pressing the right mouse button in the CDM MESSAGE LOG window: the problem appears on the NvDM/2 V2 at CSD XR20302 (June 93 level). Hereafter the menu that is prompted: |---------------| | COPY | | CUT | | PASTE | |---------------| | DO IT | | SHOW IT | |---------------| | SAVE | | AGAIN | | EDIT -> | | SMALLTALK -> | ----------------- COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The context menu will no longer appear. PTRNBR: 2M03501 APARNBR: PJ09636 PTFNBR: XR20334 EXTERNAL SYMPTOM: SEND OF FLATDATA FAILS BECAUSE NO EOF OR CRFL . PROBLEM SUMMARY : This problem has been found by a customer (Los Angeles Unified School) . When trying to CDM SEND either of 2 files up from NVDM/2 to the host, ANX1262 SEND failed because it could not transform the object between fixed and variable formats is received. The error manual says that ANX1262 means that the length of the object and the length stored in the catalog are different. Oh, also MESSAGE.DAT contains the following after the NVDM 1.4 plan hangs: ANX0698: (E) a SNA/FA Server Operation failed with return code 085A0000 I've read the message description however, the file does exist on the PC under the local name as cataloged and while there is a NVDM 1.4 resource definition for this file (the same that's used for the other 9 LAUSD.TEST.*.*.* the *.*.* is replace with CLASS.LAUSDNET.T024N where LAUSDNET is the NETID and T024N is the LUNAME), it does not reside in the Repository. These same conditions/specifications work for 8 out of the 10 files. The files do not contain, at the end, either the CRFL (x'0D0A') nor the EOF (x'1A'). If the file ends with CRFL or EOF or both, the file is correctly sent. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem occurs only when the txt file sent (Uniform Text) doesn't contain, at the end, either the CRFL (x'0D0A') nor the EOF (x'1A'). In this condition the Specific Server doesn't recognize the end of file. After fix the Specific Server recognizes the end of txt file checking the size of file. PTRNBR: 2M03526 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: CDM QUERYCF:TRAP WHEN THE CHANGE FILES CONTAINS MANY FILES PROBLEM SUMMARY : When attempting to list the files contained in a change files with about 3000 entries, the CDM QUERYCF command fails. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The CDM QUERYCF command changed to correctly handle reset of a list. PTRNBR: 2M03627 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: DIALOG: THE 'INCLUDE' MENU ITEM WITH 'REFRESH' OPTIONS PROBLEM SUMMARY : If you choose 'INCLUDE' in the CDM Catalog window menu bar and specify the option 'refresh', all the entries are displayed. It sounds like, first the global name are selected and then they are refresh with all those that are in the Catalog I expect the Dialog first to get all the entries from the Catalog and then to select according to the user filter COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Now remembers the filter when the refresh is done. PTRNBR: 2M03658 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: PMR 0X222 : ANXCKPUQ.DLL HAS A TRAP D DURING THE INSTALL WITH REMOVABILITY OPTION. PROBLEM SUMMARY : When an install with removability option is executed on a Change File such that the sum of all characters for all the packed path files names exceeds 64k, the install execution fails due to a TRAP D in the ANXCKPUQ.DLL module. This is the Operating System Trap D panel : A program generated an access violation at 19a3827f ANXCKPUQ.DLL 0005:01cf755d P1 = 00000008 P2 = 00004d5c P3 = XXXXXXXX P4 = XXXXXXXX EAX = 00003038 EBX = 00000000 ECX = 00000004 EDX = 000000cf ESI = 000000cf EDI = 0000343c DS = 00cf DSACC = 000000f3 DSLIM = 0000ffff ES = 006f ESACC = 000000f3 ESLIM = 0000ffff FS = 150b FSACC = 000000f3 FSLIM = 00000030 GS = 0000 GSACC = ******** GSLIM = ******** CS:EIP = cd47:00002b83 CSACC = 00fb CSLIM = 00003963 SS:ESP = 006f:0000f3a6 FSACC = 00f3 SSLIM = 0000ffff EBP = 0000f3a3 FLG = 00012203 COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: The problem occurs at the Back-Up change file build time, when the Agent/CM invokes the Pack/Unpack service to build the Back-Up Change file before installing the Change File. The problem really depends by the fact the sum of all characters in all the path file names packed in the Change File, which is to be backed up, is grater than 64K. This situation, even if not properly managed in the code,as the current ptr evidences, is a documented design limit in the Pack/Unpack service at the install with the removability option time. The called out documentation is the NvDM/2 User's Guide. The fix for the current problem avoids the TRAP D occurrence when the limit is reached and it allows to build Back-Up Change File without any limit in the characters number in the path file name in the source Change File. PTRNBR: 2M03667 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: IFS DRIVER IS TO BE LOADED EVEN IF STORED IN A NETWORK DRIVE PROBLEM SUMMARY : When an user try to load the file system driver ANXIFCOM.IFS during a remote IPL (RIPL) the fyle system driver is not loaded and a SYS01719: the file system does not contain a valid device or file system driver COMPONENTS CHANGED OR ENHANCED: ANXIFCOM.IFS PROBLEM CONCLUSION: The initilization of the IFS file system driver used a system call that does not work with redirected drive. Thus the system call has been substituted by a different one able to manage remote drivers. PTRNBR: 2M03679 APARNBR: XXXXXXX PTFNBR: XR20334 EXTERNAL SYMPTOM: MESSAGE TEXT OVERWRITES THE DISPLAYED BOX WINDOW PROBLEM SUMMARY : While performing a NvDM/2 unattended installation from images on fixed disk , if the error message text is long it overwrites the box-window border in which it is displayed. COMPONENTS CHANGED OR ENHANCED: SBODY.EXE BODY.EXE PROBLEM CONCLUSION: Only the first 4 row of the message are dislpayed PTRNBR: 2M03722 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: PMR 9X106 : BAD MANAGMENT ON FILE SIZE IN DECOMPRESSION DURING A CHANGE FILE INSTALL PROBLEM SUMMARY : Unpacking the system file such as Drive\OS2\MDOS\WINOS2\SYSTEM\XLAT861.BIN, with the file size 407 bytes, the unpack service provides back a CRC error on the Change File containing the compressed file. The install function ends with an unrecoverable error. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL NVDMLZW.EXE PROBLEM CONCLUSION: The problem was discovered in decompression routine due to the fact the compressed file size for this special file equals the uncompressed file size. This problem is file dependent. It can be reproduced using a file such that its size equals the size of its compressed version in the Change File. PTRNBR: 2M03731 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: PMR 5X544 : T.C BAD TIMER MANAGMENT PROBLEM SUMMARY : When the machine is left with the product running without doing anything for many hours, the T.C is unable to process the work to do, i.e a send from Host to node. The Host plan remains executing and the distribution going from Host to node is really not received by the T.C. . The problem is very random and machine dependent. There is no way to manually reproduce the problem. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The problem is due to a bad managment on system machine time. In particular a anxsnads.exe module was unable to manage the situation for which the operating system interrupts the process in the module and gives it back the cpu control after some moments. The effect for this situation is an internal loop which can exist for many hours or indefinitively. PTRNBR: 2M03747 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: CHANGE CONTROLLER FAILS W/REQUEST QUEUED BEFORE START PROBLEM SUMMARY : Description: Enqueueing an install request to the Change controller while it was stopped. Then tried to start the change controller by issuing a CDM START command. The change controller started and then after a few minutes ended with errors. The only way to recover the machine was to reboot it. If the same install request is issued while the change controller is active, it is processed correctly. COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.EXE ANXIFSRV.DLL ANXIFREQ.DLL PROBLEM CONCLUSION: On Server side ANXIFS is divided in two parts: ANXIFSRV.DLL and ANXIFSRV.EXE. The EXE is started by a DosExecPgm with EXEC_BACKGROUND parameter. A shared segment is used by the DLL and the EXE to communicate. Moreover when the DLL sees the shared segment allocated it supposes the server is running. In some particular cases the EXE was stopping while the DLL was asking it to restart, but when it wrote on the shared segment the EXE was no more running. So also if the segment was present the EXE was not able to continue its work (it was not running||) so it was impossible to continue working. Moreover some other things were improved such as the closure of all semaphores created by the EXE before exiting it... Then changed something in the DLL so that now an ANXIFS stop will be performed ONLY after the EXE is fully active and ANXIFS restart will be performed ONLY if it has been requested BEFORE the stop is unrecoverable. If a restart is requested after the stop is in a not recoverable state a completely new EXE is started. PTRNBR: 2M03758 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: DIALOG: EXPORT DOES NOT WORK OK FOR PARMS WITH '=' CHARS PROBLEM SUMMARY : "Catalog Change file" dialog - "Export" pushbutton if Params contains characters like '=', SECTION, Install, Catalog, Begin, End when it is exported it produces a change file profile like this (for instance, if it contains '=' character Begin Program = PROG.EXE Parms = /S=$(SourceDir) End If this new profile is used by "Build from profile" button, it FAILS because '=' is seen as a special character. In order to work, the Parms value must be put between quotes with an editor. This is unacceptable if the customer does not want to use an editor. The dialog should AUTOMATICALLY put the right part of the assignenent (i.e. the key value) between quotes if it contains those special chars or blank and if the Customer has put a quote in the value, this should be automatically doubled. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Now put " " around the parms. PTRNBR: 2M03762 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: CMD.LINE: WILD CHARS DO NOT WORK IF TOKEN IS &DATETIME PROBLEM SUMMARY : Having a global name such as: A.B.C.&DATETIME and sending it using the wild chars CDM SEND A.B.C.* the command fails because no match is found in the catalog. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: Transform Handler is called from Command Line to search the Global Name token string into the FS catalog. TH checks if there is a token with "&DATETIME" specified but in this scenario TH finds "*" character in correspondence of "&DATETIME" token. This generate a wrong "&DATETIME" handling. Transform Handler gets the unique entry in the FS catalog using the Global Name token string with "*" char. If the obtained unique entry has "&DATETIME" token in correspondence with "*" char token, TH sets properly the searching_indicator to handle the "&DATETIME" token. PTRNBR: 2M03825 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: DOCUMENTATION: MESSAGE 1121 TO BE CHANGED PROBLEM SUMMARY : Message 1121 should be changed as follows: The command for object global name %1 cannot be executed because the local file %2 is in use or is read-only. Explanation: When trying to access the local file associated to the named global name in the current command, the local file is found inaccessible System action: the command is unsuccessfully completed User response: Check if the named local file is read-only or in use or the path is accessible COMPONENTS CHANGED OR ENHANCED: ANX.MSG ANXH.MSG PROBLEM CONCLUSION: ANX.TXT. ANXH.TXT and documentation changed. PTRNBR: 2M03833 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: AGENT ABEND IF A PACKAGE CONTAINS /C IN FILESPECLIST PROBLEM SUMMARY : In CSD XR203023, an object with such a filespec list djltest/proc/*.cmd djltest/dll/*.dll config.sys /C startup.cmd /C is installed with removability while Agent ends because of errors. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: The problem occurs during the install of a change file having in it files with the /C option which they really existed at build time. The provided fix solves the problem at the install time and no change file rebuilt is requested. PTRNBR: 2M03849 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: LIMIT IN NUMBER OF IN/OUT CHARS IN DIALOG FIELDS PROBLEM SUMMARY : Tring to execute a build from the Dialog panels the "Source Directory" input field allows only 32 characters while command line does not raise any limit. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Updated these entry fields to the maximum length allowed by the request block api. PTRNBR: 2M03902 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: SEND FAILS IF OBJECT SIZE ABOUT 2K BYTES PROBLEM SUMMARY : Customer describes this scenario: 1) SEND data from Host to NvDM/2. Size of file sent is 2424 bytes. 2) SEND operation fails with ret code 8 (SNACR=085A0000 from node) 3) MESSAGE.DAT ====> ANX0082 msg (SNA/FS Server error) 4) ERROR.DAT ====> Error in ANXBFP13 MODULE with rc 20,0. The error is due to FILE STORING. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem arises when the sent object is completely contained in a SNADS buffer (2560 bytes) but the suffix of the FS_Server_ Request (12 characters) is split in the next SNADS buffer. NOTE: the SNADS buffer (2560) contains the header of file so the problem depends on size and on header of file (global name for examplr). We have reproduced the error with a file.SAF of 2570 bytes. The problem is fixed adding a new status (7) in the Specific Server Read Status Machine. This new status handles the particular scenario described above. PTRNBR: 2M03934 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: ANX0644 MSG WITH APPC_SENSE_DATA IF 'ALLOCATE' VERB PROBLEM SUMMARY : A better APPC error handling by Transmission Controller is required from the customers. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: This fix adds the APPC Sense_Data at APPC ALLOCATE verb return code end it allows a better APPC Error handling. When an error is returned from Basic Conversation APPC verbs to the Transmission Controller, TC issues the ANX0644 msg. PTRNBR: 2M03941 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: BUILD ASKS FOR DISKETTE IF DEVICE IS LOCKED PROBLEM SUMMARY : When applications like PM Seek and Scan (of ES 1.0) locks the drive where the change file to build is to reside, then the Build asks to insert a diskette. This is because the External Interface is not able to access that device to check whether it was a diskette drive; OS/2 API returns ERROR_SHARING_VIOLATION to External Interface. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL ANX.MSG PROBLEM CONCLUSION: The external interface is going to issue another message (both command line and dialog) ANX01251 (E) <command> failed because the drive <drive:> was in use by another application. Explanation: The CDM command cannot access the named drive because there is another application that is using it by denying the access to other applications. The command terminates unsuccessfully. PTRNBR: 2M03131 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: NON STOP BRADCASTING IF CC SERVER IS DOWN PROBLEM SUMMARY : Having a lot of CC clients active and CC server down could be deadly: if the AttachTimeOut value (client side) is -1 and server is down CC clients send a lot of requests to the server so saturating the LAN. COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.EXE ANXIFREQ.DLL PROBLEM CONCLUSION: The idea of old ANXIFS (before this fix) was the following: Client asks for an attach; if the attach is successful go on otherwise the CC Server is recognized not running or not able to process a request (because at MaxClients or an ANXIFS shutdown has been requested), client waits for a few seconds and then tries another attach. Of course if we have a lot of clients asking for an attach and server is down we can have the problem explained in PTR text. The design was changed as follows: client asks for an attach for 3 times (maximum); if the attach is not successful for one of the reasons above explained,Client stops sending attach request and waits for a signal from the server. On the server side we have the following: when server becomes active,it signals to the clients it is ready to process request. So if some client was in waiting state they wake up and ask for an attach. Server also send a signal when there are no more MaxClients clients attached and so it is ready to process another attach and another request. PTRNBR: 2M03161 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: DOS CC Client Installation: NetBIOS check fails PROBLEM SUMMARY : If NetBIOS is not installed on the DOS target machine, the DOS CC Client installation completes successfully instead of terminate displaying error message ANX7210 (NetBIOS not installed). COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE PROBLEM CONCLUSION: Call the NetBIOS interrupt passing the proper input parameters. PTRNBR: 2M03173 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: DOS CC Client File Only Installation: the termination message is not displayed on the screen. PROBLEM SUMMARY : When the DOS CC Client file only installation completes successfully the termination message is logged but not displayed. COMPONENTS CHANGED OR ENHANCED: NVDMIDFO.EXE PROBLEM CONCLUSION: Before print the termination message on the screen position the cursor at the second row instead of the first; in this way the message will not be erased by the OS/2 help line. PTRNBR: 2M03279 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG MSG WHEN 2 CLIENTS HAVE THE SAME NAME IN THE NETWORK PROBLEM SUMMARY : If both OS/2 and DOS NvDM/2 clients use the same name in the same LAN an unexpected error is logged by the OS/2 client. COMPONENTS CHANGED OR ENHANCED: ANXCMLDR.COM ANXCSCNS.DLL ANXCSCNN.DLL ANXCSCNP.DLL ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: The problem was due to a design error. The DOS and the OS/2 clients were using different NetBIOS names. Now each of them is aware of the other client's name and can signal the user an inconsistent condition. PTRNBR: 2M03437 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: DIALOG:PHASE END BUTTOM NOT CHECKED PROBLEM SUMMARY : If in a Change File Profile the PhaseEnd field value "YES" is different from lower case (i.e. UPPER or MIXED) the PhaseEnd button is not checked out when you open the object after having created it form Build Profile. Moreover if the new object is used to Export and create another profile the PhaseEnd is not exported. Everything works if the value is "yes". COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Now handled mixed and upper cases. PTRNBR: 2M03475 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: DBCS: ERROR MESSAGES LOGGED AFTER CDM SHUTDOWN PROBLEM SUMMARY : After that the command CDM SHUTDOWN is successfully performed, no error messages should be logged. The problem is that the following error messages are logged in the ERROR.DAT: ** NetView DM/2 logged at 11:36:06 20/08/1993 * Error detected in NetView DM/2 CM component. The error was generated in module ANXACCDO. Additional Data : 41 4e 58 41 43 43 44 4f 30 30 31 31 44 6f 73 54 ANXACCDO0011DosT 68 72 65 61 64 52 45 43 45 49 56 45 01 00 01 00 hreadRECEIVE.... 0b 00 30 30 4e 45 54 42 49 4f 53 ..00NETBIOS ** NetView DM/2 logged at 11:36:06 20/08/1993 * Error detected in NetView DM/2 CM component. The error was generated in module ANXACCDO. Additional Data : 41 4e 58 41 43 43 44 4f 30 30 31 31 44 6f 73 54 ANXACCDO0011DosT 68 72 65 61 64 4b 69 6c 6c 54 68 72 65 61 64 01 hreadKillThread. 00 01 00 34 00 30 30 4e 45 54 42 49 4f 53 ...4.00NETBIOS COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: In order to eliminate these needless logs the Change Controller will not log for some particular Netbios Return Codes. PTRNBR: 2M03506 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG CHARACTERS IN ANXIDCFO.LOG ON JAPANESE MACHINE PROBLEM SUMMARY : The file ANXIDCFO.LOG created by NVDMIDCFO procedure contains some wrong character in the division line. COMPONENTS CHANGED OR ENHANCED: NVDMIDFO.EXE PROBLEM CONCLUSION: The double bar that separes log messages was not written with DBCS characters. Now if the machine has a DBCS code page,the bar will be written with the correct characters. PTRNBR: 2M03537 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: MISSING HELP ON "ORDER" PUSH BUTTON ON INSTALL DIALOG PROBLEM SUMMARY : The "Order" push button on the Install dialog does not have any help associated with it. (Catalog -> Selected -> Install). COMPONENTS CHANGED OR ENHANCED: ANXEDTCA.HLP PROBLEM CONCLUSION: Added install order help. PTRNBR: 2M03538 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: MISSING ACTION BAR ITEM HELP PANELS PROBLEM SUMMARY : Help panels are missing for the Action Bar Item "Help" on all the Main Windows for the Dialogs (Catalog, CC Domain, Remote Dest., Message Log). COMPONENTS CHANGED OR ENHANCED: ANXEDTCA.HLP ANXEDTCL.HLP ANXEDTRN.HLP ANXEDTML.HLP PROBLEM CONCLUSION: Added help templates. PTRNBR: 2M03541 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: HELP MISSING FOR "HELP" MENU PULL DOWN ITEMS PROBLEM SUMMARY : All the pull down items from the "Help" menu bar are missing help panels (Index, General Help, Using Help, Keys Help, About). This is true for all the Main Windows (Catalog,CC Domain,Remote, Destinations, Message Log). Also, the Help menu bar item is missing it's help panel. COMPONENTS CHANGED OR ENHANCED: ANXEDTCA.HLP ANXEDTCL.HLP ANXEDTML.HLP ANXEDTRN.HLP PROBLEM CONCLUSION: Added help templates.... PTRNBR: 2M03561 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: HELP FOR ANXI5195 IS UNUSABLE PROBLEM SUMMARY : Pushing on the Help button of the informational message ANXI5195 that appears starting the Dialog, the Help panel subsequently displayed disappears quickly and doesn't allow the customer to read the informations written in it. This panel should be removed from the screen at customer request as well as for all of the other Help panels,otherwise it becomes practically unusable. COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.MSG CDMD.EXE PROBLEM CONCLUSION: Removed the help button from the startup dialog since it is not necessary for an informational message as described on CUA Advanced Interface Design Reference. PTRNBR: 2M03562 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: INCORRECT GENERAL HELP FOR REMOTE NODE "OPEN" DIALOG PROBLEM SUMMARY : The General help panel for Open Remote Destination is incorrect. The "New Remote Destination" help is displayed. Double click on any RN in the remote destinations window. Press the help push button. The incorrect help is displayed. COMPONENTS CHANGED OR ENHANCED: ANXEDTRN.HLP PROBLEM CONCLUSION: Added new helps for Open. PTRNBR: 2M03594 APARNBR: PJ11653 PTFNBR: XR20334 EXTERNAL SYMPTOM: ANXEDINI: THE HELP HEADERS CONTAIN THE STRING NDM/2 PROBLEM SUMMARY : All of the HELP header of ANXEDINI contain the string "NDM/2". It is STRONGLY recommended to change this string in "NvDM/2" or, better, in "NetView DM/2" COMPONENTS CHANGED OR ENHANCED: ANXEDINI.EXE PROBLEM CONCLUSION: NetView DM/2 must be used and not NDM/2 PTRNBR: 2M03597 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: LOOP OF ANX0211 AFTER ACCEPT WITH DELETED .REM FILE PROBLEM SUMMARY : If after a removable install in active, the related cmfxxx.rem file is deleted, when you try to Accept the entry, the message ANX0211 (unrecoverable error) is undefinitively stored in the message.log . COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The condition in which the file cmf****.rem does not exist is now correctly managed in ACCEPT and in REMOVE functions by message anx0220. More the message loop caused by a not correctly management of the return codes 20 0 (unrecoverable condition) is fixed by setting for these conditions the error_flag = on in module ANXACPA1. PTRNBR: 2M03611 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG SENSE CODE 100B0006 PROBLEM SUMMARY : When an install operation with seconday effects is performed from the Host the report that will be returned to it is wrong. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE ANXLASD.DLL PROBLEM CONCLUSION: In order to cover a bug in the Parser e Builder component the Agent code is changed. PTRNBR: 2M03641 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG CHARACTERS IN MESSAGE.DAT AND ANXINST.LOG ON A KOREAN MACHINE PROBLEM SUMMARY : For a Korean DOS Client with DOS 5.03/V and codepage 934 or 949 the bar that divides the messages in MESSAGE.DAT and ANXINST.LOG contains some wrong characters. A conversion from SBCS to DBCS character set is needed before printing the log bar. COMPONENTS CHANGED OR ENHANCED: ANXCMAUT.EXE ANXCMBOT.EXE ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE ANXCMEXE.EXE ANXIDMCF.EXE ANXIDRCF.EXE ANXLOCKF.EXE CDM.EXE NVDMIDFO.EXE NVDMIDOS.EXE NVDMUPD.EXE PROBLEM CONCLUSION: The log separator bar is converted correctly from SBCS to DBCS character set, when needed. PTRNBR: 2M03655 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: ADD COMMENTS IN CHG FILE PROFILE PROBLEM SUMMARY : This a useability requirement to allow End User to add comments in a change file profile. COMPONENTS CHANGED OR ENHANCED: ANXEFQ2S.DLL (ANXEFAPI.DLL) ANXEFQ3S.DLL (ANXEFAPI.DLL) ANXEFQ4S.DLL (ANXEFAPI.DLL) PROBLEM CONCLUSION: Now the End User can add comments to your change file profiles by prefixing the comment line with a semicolon. PTRNBR: 2M03719 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: SYSTEM ABEND 2 UNDER STRESS PROBLEM SUMMARY : A System Abend 2 occurs at remote CC Servers when submitting a plan from HOST that send 15 type of resources with different sizes but same compression alghoritm, NVDMLZW. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL. PROBLEM CONCLUSION: The problem was discovered in a bad way to manage the return codes from the compression/decompression routines. PTRNBR: 2M03727 APARNBR: PJ11654 PTFNBR: XR20334 EXTERNAL SYMPTOM: BAD MANAGMENT ON FILE SIZE IN DECOMPRESSION PROBLEM SUMMARY : Unpacking the system file <drive>:«OS2«MDOS«WINOS2«SYSTEM«XLAT861.BIN, with the file size 407 bytes, the unpack service provides back a CRC error on the Change File containing the compressed file. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: The problem was discovered in decompression routine due to the fact the compressed file size for this special file equals the uncompressed file size. This problem is file dependent. It can be reproduced using a file such that its size equals the size of its compressed version in the Change File. PTRNBR: 2M03770 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: NO SENSE CODE SENT TO HOST PERFORMING SEND/INSTALL FUNCTION PROBLEM SUMMARY : Assume to submit from HOST an Install/Send request to the Server node and the Install is addressing an invalid drive of the Server node. The request unsuccessfully ends on the Server node and the right message is logged on the message.dat, but on the Host side the Agent report code=0 and Server report code=0 are sent. COMPONENTS CHANGED OR ENHANCED: ANXCAQ4C.EXE (ANXCMCLC.EXE) ANXCAQ4S.EXE (ANXCMCLS.EXE) ANXCAQ3S.EXE (ANXCMCLS.EXE) ANXCAPMC.EXE (ANXCMCLP.EXE) PROBLEM CONCLUSION: The problem is due to instruction missing. It has been added the SNACR setting (084C0008) when you try to install on a invalid drive. PTRNBR: 2M03783 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE MESSAGE ANX1530 HAS TO BE CORRECTED PROBLEM SUMMARY : The text of the message ANX1530 must be corrected in 'The command issued is invalid. No filename was specified in <Inputpath>'. COMPONENTS CHANGED OR ENHANCED: ANX.MSG PROBLEM CONCLUSION: The message "ANX1530" in the anx.txt file must be changed in the following new one: "ANX1530: The command issued is invalid. No filename was specified in "pathname" PTRNBR: 2M03835 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: MISSING AUTOEXEC AFTER A CDM STOP ON SERVER PROBLEM SUMMARY : Assume to issue a series of CM requests on 2 CC Clients and during the execution to stop the Server. On the CC Clients machine the following message "System executing a configuration recover process. Please wait..." appears when the Clients try to attach the Server. After that,the AUTOEXEC.BAT on the CC Clients is 0 byte and the correct one is under the directory BIN (AUTOEXEC.USR). COMPONENTS CHANGED OR ENHANCED: ANXIDRCF.EXE PROBLEM CONCLUSION: The program ANXIDRCF.EXE didn't restore correctly the user AUTOEXEC.BAT building the saved AUTOEXEC.USR pathname wrong. The correct pathname has been set so it can restore the user AUTOEXEC.BAT correctly. PTRNBR: 2M03847 APARNBR: PJ11655 PTFNBR: XR20334 PROBLEM ABSTRACT: RIPL: Dummy Directory Check for Only External Installation PROBLEM DESCRIPTION: When an External Installation runs,NetView DM/2 checks the validity of Target Directory, but actually this target directory could be never used (for instance in a RIPL environment). EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: Now,the check is done only if A FileSpecList Section is defined. PTRNBR: 2M03851 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: DATE AND TIME NOT DISPLAYED FOR A COREQ IN LIST COMMAND PROBLEM SUMMARY : Install a primary object and a corequisite, then while the install request is pending issue a CDM LIST command for the corequisite object, the fields DATE and TIME aren't filled. COMPONENTS CHANGED OR ENHANCED: ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The Date and Time was not filled into the CM table for the corequisite. The problem was due to instructions missing. The problem has been solved adding codes to set in DataBase the date/time also for the corequisite. PTRNBR: 2M03874 APARNBR: PJ11655 PTFNBR: XR20334 PROBLEM ABSTRACT: EXTERNAL INSTALL HARD ERROR ABORT BAD MANAGEMENT PROBLEM DESCRIPTION: If one of the corequisite got an hard error abort during an external Install,NetView DM/2 continues with the other corequisites. EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: Hard Error Aborts,now,cause the execution of the corequisites sequence to be interrupted. PTRNBR: 2M03885 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE OS/2 PRISTINE PANEL IS UNREADEBLE ON MONOCHROMATIC DISPLAYS PROBLEM SUMMARY: Server and client name fields of the OS/2 pristine machine panel are unreadable on a monocromathic display. A correct color attribute should be chosen to allow user interaction. COMPONENTS CHANGED OR ENHANCED: ANXPULAG.EXE PROBLEM CONCLUSION: Now, a check about adapter type,display type and display mode,is performed;if the video is monochromatic, video attributes are properly set. PTRNBR: 2M03888 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: DIR NOT DELETED ISSUING A REMOVE REQUEST WHEN DISK IS FULL PROBLEM SUMMARY : Issue a remove request on a DOS client,when the disk is full, the request successfully ends but the directory of the removed package isn't erased on the client. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: Now, after deleting the files/directories the remove request results successfully completed. PTRNBR: 2M03889 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: PMR0X494:UNRECOVERABLE ERROR DURING INSTALL PROBLEM SUMMARY : During the Unpack Process of a specific file built with /T option the CDM Agent goes down reporting a Primary Error 0 from Unpack. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: The problem comes out during the file compression at the change file build time. The problem is now fixed. Unfortunately, to recovery Customer occurrences, a new build of the original change file is necessary later to have implemented the new ANXCKPUQ.DLL . PTRNBR: 2M03892 APARNBR: PJ11655 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE OS/2 PM INSTALLATION FAILS WHEN THE TARGET DIRECTORY HAS ATTRIBUTES OTHER THAN DIRECTORY SET PROBLEM SUMMARY : If an attribute is set for a directory using the File Manager capabilities (i.e. ARCHIVE attribute set), when the user tries to install the product under this directory the following error appears: 'The Target Directory field contains the name of an existing file. Type a valid directory name.' COMPONENTS CHANGED OR ENHANCED: NVDMPMS.EXE NVDMPMC.EXE NVDMEPMS.EXE PROBLEM CONCLUSION: The Target Directory check has been corrected: now the installation simply verifies that the value specified refer to a directory (i.e. the DIRECTORY flag is set), without regard to other attributes setting. PTRNBR: 2M03894 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: A NEW KEY IS NEEDED TO SUPPORT THE RULE FILES MIGRATION PROBLEM SUMMARY : A new key is needed in the DOS installation to support the Rules Files migration. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE PROBLEM CONCLUSION: The building process of minimal configuration files is executed using two rule files: ANXIDMCF.AUT for minimal AUTOEXEC.BAT file and ANXIDMCF.CNF for minimal CONFIG.SYS file; if the workstation has a configuration not described in the rule files, the user can modify the rule files adding the rules related to the specific configuration of the workstation. The rule files modification can be done manually, using an editor, or using the NVDMUPD program through a modification file; changes can be tested using the ANXIDMCF program with the /TEST parameter. The above scenario has a limit: when reinstalling the product, the user must save the modified rule files, or they will be replaced by the default ones. To bypass this limit and allow a better management of the DOS client workstations the product installation has been modified to allow rule files migration during a reinstallation. A new parameter, /RRF, and the correlated response file key, RestoreRuleFiles, has been introduced; the parameter is of SWITCH type, so only YES and NO values are allowed for it, being NO the default. The parameter is significant only during a reinstallation or configuration, while has no effect during the first installation. Now after product installation the backup copy of the default rule files (ANXIDMCF.BKA for ANXIDMCF.AUT and ANXIDMCF.BKC for ANXIDMCF.CNF) will be placed under the BIN directory of the product. PTRNBR: 2M03900 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: HELP (F1) RECURSIVE PROBLEMS PROBLEM SUMMARY : At CDM Catalog - double click on a catalog entry. At the Catalog Change - click on INSTALLATION. At the Installation Dialog - click on the target directory text area and push F1 for help: repeat several times if it does not fail the first time. The results of the above steps are TRAPS and hang conditions and recursive operations that cause the PM to run out of resources. To recovery from above events could become needed to shutdown NvDM/2 or reboot the machine. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The problem was due Dialog, now fixed. PTRNBR: 2M03908 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: STRESS SCENARIO: TRAP ON THE SERVER AFTER 100 CM INSTALL PROBLEM SUMMARY : After a lot of install requests the ANXLCPB.DLL goes in trap. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE ANXLCPB.DLL PROBLEM CONCLUSION: The problem was due to an incorrect management of the return codes of the ANXCSPM0. This module allocate memory and in the DLL the return codes returned by this module are not checked well. Now in case of return codes different from 0, the module ANXCPPIT will return to the caller the rc 20 00 and in this case the calling module will not execute the terminate_encode operation. PTRNBR: 2M03909 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: SOME DOS CLIENTS HANG DURING A LOT OF INSTALLS PROBLEM SUMMARY : Assume the following stress scenario: hundreds of CM requests on 16 cc clients (os/2 and dos). Some machines, after few installs, hang after the build of minimal configurations; the following messages are displayed: Dos NvDM/2 minimal configuration file builder... Execution in progress.... ...Execution ended successfully). Some machines hang on the CDM Agent panel. A manual IPL is needed to start these machines. COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.EXE ANXCMBOT.EXE PROBLEM CONCLUSION: Analyzing this problem has been found out that the hang occurs in the reboot routine called by the CDM Agent Loader. In order to solve this problem some changes have been done in the ANXIDMCF and ANXCMBOT executable files. PTRNBR: 2M03913 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: NO ERROR DISPLAYED WHEN THE SECTION IS WRONG PROBLEM SUMMARY : In a DOS CC Client multiconfigurated, the section containing the NetBios device is named NvDM2. If the following rule is used: $ <Section Name Wrong (es: NDM)> Device Œ© An error during the minimal configurations building should be displayed,$ indicates a mandatory rule, but the program ends successfully and the NetBios drivers aren't loaded. COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.EXE PROBLEM CONCLUSION: Now the error is displayed. PTRNBR: 2M03914 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: ANXLOCKF LOG WITH UNDELETED FILES PROBLEM SUMMARY : Unneeded messages logged in ANXLOCKF.LOG when reinstalling DOS CC Client to refresh. The messages involved are: *******ANXLOCKF.LOG ANX1806: (E) An unexpected DOS error SYS0002 occurred deleting file C:\IBMNVDD2\BIN\ANXNVDM2.BAT. ANX1806: (E) An unexpected DOS error SYS0002 occurred deleting file C:\IBMNVDD2\BIN\COMMAND.COM. COMPONENTS CHANGED OR ENHANCED: ANXLOCKF.EXE PROBLEM CONCLUSION: The above messages are no longer logged. PTRNBR: 2M03919 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG CHARACTER BEFORE ERROR LOG TIMESTAMP PROBLEM SUMMARY: When a parsing error occurs before installation log file validation, an extra character is written before the timestamp related to the error message in the message log. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE PROBLEM CONCLUSION: The presence of the character before the timestamp was due to a wrong log header printing; the print instruction has been corrected. PTRNBR: 2M03920 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: MISSING CHECK ON RESPONSE FILE KEYS PROBLEM SUMMARY : If in the response file a key is duplicated, no error message is displayed and the installation continues processing. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE PROBLEM CONCLUSION: The problem was due to an invalid key definition check, now corrected. PTRNBR: 2M03925 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE CM REQUEST PANEL DOES NOT DISAPPEAR EVEN IF THE SPECIFIED TIMEOUT IS EXPIRED PROBLEM SUMMARY : During a stress scenario (the installation of 300 packages on 10 clients) a DOS Client workstation sometimes hangs when the panel of the CM request is displayed. COMPONENTS CHANGED OR ENHANCED: ANXCMLDR.COM PROBLEM CONCLUSION: The defect was due to a malfunction of the timer interrupt that does not allow the TSR to remove the request panel at the right time. The problem has been fixed improving the timer interrupt routine. PTRNBR: 2M03930 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: INVALID LINE DISPLAYED WHEN A SYNTAX ERROR OCCURS PROBLEM SUMMARY : An invalid line is logged in the modification log file when a syntax error occurs in the rule files. The line displayed in the log file is the right one + 1. COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.EXE PROBLEM CONCLUSION: Now the line displayed is the right one. PTRNBR: 2M03931 APARNBR: PJ11657 PTFNBR: XR20334 EXTERNAL SYMPTOM: NVDMRESP.RSP FILE MUST BE REVISED PROBLEM SUMMARY : The NVDMRESP.RSP in the fourth diskette of NVDM/2 (Extended Package) must to be revised: - It needs to split it into 3 different parts (for CC Server, CC Client OS/2 and CC Client DOS Installation) - Add the keys related to CC DOS Client Installation - "FileServiceDir = C:«IBMNVDM2«FSDATA" is wrongly written, there is a wrong character (similar to 1/2) instead of the backslash between IBMNVDM2 and FSDATA COMPONENTS CHANGED OR ENHANCED: NVDMRESP.RSP PROBLEM CONCLUSION: NVDMRESP.RSP has been modified. A copy of this, is located on the last CSD diskette labelled CC Server & OS/2 CC Client APAR FIXES. PTRNBR: 2M03942 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: CHANGES IN SOME MESSAGES PROBLEM SUMMARY : The messages anx0262, anx0288 and anx1064 have to be changed following Washington System Center (Charlie Brown) comments. COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.EXE ANXIFSRV.DLL ANXIFREQ.DLL ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) ANXCAQ4C.EXE (ANXCMCLC.EXE) ANXCAPMC.EXE (ANXCMCLP.EXE) ANXCSCNS.DLL ANXCSCNN.DLL ANXCSCNP.DLL ANXPULAG.EXE PROBLEM CONCLUSION: The problem is due to bad use of messages for function that interface NetBios. Charlie Brown asked us to improve the messages when a "Not Enough NetBios Resource" problem occurred. The appropriate messages have been changed and added for this function and now provide some more information in the situation above described. Now the messages say which resource are lacked and how many resource the Customer have to add in the his configuration file. PTRNBR: 2M03944 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: HOW TO INSTALL DOS CC CLIENT OVER PC EQUIPPED WITH 5.25 DRIVER PROBLEM SUMMARY : Need to create 5.25 diskettes, not more distributed with product packages, from 3 1/2 ones. COMPONENTS CHANGED OR ENHANCED: NVDMCSDK.CMD README.TXT PROBLEM CONCLUSION: NVDMCSDK procedure is either documented in the NvDM/2 Version 2 Installation and Customization Guide SH19-6915-03(chapter 1: Identifying your environment),distributed as softcopy with this CSD, and the current CSD README.TXT file. The utility is located on the last CSD diskette labelled CC Server & OS/2 CC Client. PTRNBR: 2M03949 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: UNRECOV. ERROR ON CDM INSTALL ON A CLIENT IN STRESS SCENARIO PROBLEM SUMMARY : Assume a stress scenario that executes a tool that submits automatically a series of CM functions, resets the situation and restarts from the beginning. Executing a CDM INSTALL SOFTWARE.INRU.CHECK.UPD.1.2 /R:Y /DA:S on a CC OS/2 Client an unrecoverable error prevents continuation of processing and the Change Controller ends because of errors, but the resource results installed IRA at the CC Client even if the file CMF00012.ERR is in the CMREQ subdirectory and the request id=12 is in status ABORTED. COMPONENTS CHANGED OR ENHANCED: ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The problem is due to bad managment of the condition "Already in use" of the Rename File function. The appropriate managment is now available in the code. PTRNBR: 2M03952 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: CHANGE CONTROLLER ENDS RUNNING A STRESS SCENARIO PROBLEM SUMMARY : Issue many INSTALL, REMOVE, and ACTIVATE requests on 16 Clients. After that a lot of requests ended successfully, the Change Controller ends because an Unrecoverable Error occurred. An INSTALL request abnormally ends and a CMF00908.ERR with 0 bytes is created. The following Error.dat is logged on the Server: ** NetView DM/2 logged at 06:42:32 16/11/1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPMM. Return codes were: Primary=4, Secondary=0, Auxiliary=0. Additional Data : 41 4e 58 41 43 50 4d 4d 30 30 30 31 41 4e 58 43 ANXACPMM0001ANXC 53 50 46 32 52 45 41 44 20 41 20 46 49 4c 45 20 SPF2READ A FILE 20 20 20 20 04 00 00 00 00 00 20 20 20 20 20 20 ...... 20 20 88 01 00 08 41 4e 58 43 53 30 46 42 41 4e ....ANXCS0FBAN 58 41 43 50 4d 4d 20 20 20 20 20 20 20 20 04 00 XACPMM .. 00 00 00 00 51 ce 3f 04 b8 b1 3f 04 43 4d 46 30 ....Q.?..±?.CMF0 30 37 31 33 00 00 00 00 00 00 00 00 00 00 00 00 0713............ ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ ** NetView DM/2 logged at 06:42:43 16/11/1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACCSH. Return codes were: Primary=20, Secondary=0, Auxiliary=3. Additional Data : 41 4e 58 41 43 43 53 48 30 30 30 31 53 69 67 6e ANXACCSH0001Sign 61 6c 48 61 4e 65 74 53 65 6d 57 61 69 74 00 00 alHaNetSemWait.. 00 00 00 00 14 00 00 00 03 00 5c 53 45 4d 5c 52 ..........\SEM\R 51 54 50 58 35 30 54 30 32 00 00 00 00 00 00 00 QTPX50T02....... ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ On the Message.dat the message "Unrecoverable error occurred" is logged. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: Now a simple copy function is used to copy *.cli files in *.end files. PTRNBR: 2M03955 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: IT'S IMPOSSIBLE TO INSTALL LDU RECEIVER ON A PS/2 MOD.30 DOS MACHINE PROBLEM SUMMARY : It's impossible to install the LDU receiver on a DOS client running on a PS/2 Model 30 with a 8088 processor. After issuing the NVDMIREC command, a lot of strange characters appears on the screen and a reboot is needed to restart the workstation. COMPONENTS CHANGED OR ENHANCED: NVDMIREC.EXE PROBLEM CONCLUSION: The code was compiled without enablement for 8086 - 8088 processors. The make files has been changed inserting the /G0s parameter to enable code generation also for 8086 - 8088 processors. PTRNBR: 2M03963 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE NETVIEW DM/2 GROUP NAME HAS TO BE CORRECT PROBLEM SUMMARY : The NetView DM/2 group name has to be changed writing ' ..Applications..' instead of '..Aplications..'. COMPONENTS CHANGED OR ENHANCED: BODY.EXE PMBODY.EXE SBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION: The grammathical error in the message file has been corrected. PTRNBR: 2M03968 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG MESSAGE ON THE SERVER USING DELETEWS /F PROBLEM SUMMARY : Assume to issue an Activate request on a Dos client, then, while the Activate is in progress, issue the command "DELETEWS DosClientName /F" on the Server. The workstation is successfully deleted, but on the Message.dat of the Server the following message is logged: ANX0231: (E) The Request for an Object with Global Name %1 was unsuccessful because the workstation name does not exist in the WS table. For an Activate request another message should be logged, since we don't have a GlobalName associate to the request. COMPONENTS CHANGED OR ENHANCED: ANX.MSG ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The problem is due to bad use of messages for the Activate function that does not perform operation on single workstations. The appropriate messages are been changed and added,respectively ANX0163E and ANX0259H,for this CM function. PTRNBR: 2M03974 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: WRONG INITIATE RETURN CODE AT THE HOST PROBLEM SUMMARY : The Initiate Completion Code is not returned to HOST. COMPONENTS CHANGED OR ENHANCED: ANXCMCL3.EXE ANXCMCL1.EXE ANXCMEXE.EXE PROBLEM CONCLUSION: Now the completion code is sent to the HOST. PTRNBR: 2M03999 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE MESSAGE ANX7406 IS NOT COMPLETELY CLEARED PROBLEM SUMMARY : During DOS CC Client installation, if in the AUTOEXEC.BAT there are old references to a previous installed build, but there isn't the installation directory, the message ANX7406 is displayed, but when the next message is displayed the last box line is not cleared. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE PROBLEM CONCLUSION: The message format was invalid and has been corrected. PTRNBR: 2M04008 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: MEMORY LEAK PROBLEMS PROBLEM SUMMARY : Customer USAA and Dillards are encountering many problems due to memory allocation failure. COMPONENTS CHANGED OR ENHANCED: ANXLCPB.DLL ANXSAQ2S.EXE (ANXCMSRV.EXE) ANXSAQ3S.EXE (ANXCMSRV.EXE) ANXSAQ4S.EXE (ANXCMSRV.EXE) PROBLEM CONCLUSION: The Function GetAuthorization List didn't release the memory of the list of WS, bringing in the Change Controller a leak of (300 Byte) * (num WS +1) for each signal that the signal handler received. The Parser and Builder (Module ANXLCPB) allocated the Message and error Request Block without deallocating it when it was called. This caused a leak of about: (139 Byte) * 4 * Number of remote operations. PTRNBR: 2M04015 APARNBR: PJ11658 PTFNBR: XR20334 EXTERNAL SYMPTOM: ANXIDMCF.EXE FAILS WHEN COUNTRY CONTAINS A BLANK PARAMETER PROBLEM SUMMARY : When in the CONFIG.SYS there is a statement: COUNTRY=039,,C:DOS«COUNTRY.SYS or COUNTRY=039, ,C:DOS«COUNTRY.SYS the ANXIDMCF.EXE fails and the minimal configuration isn't created. N.B. ANXIDMCF.EXE logs that the error is found at line x+1 instead that at line x COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.EXE ANXIDMCF.CNF ANXIDMCF.BKC PROBLEM CONCLUSION: The problem was caused by a wrong management of the Country statement in the Anxidmcf file. PTRNBR: 1000086 APARNBR: PJ11650 PTFNBR: XR20334 EXTERNAL SYMPTOM: ENHANCEMENT: THE MAPPING SHOULD NOT BE CASE SENSITIVE PROBLEM SUMMARY : The mapping actually is case sensitive. In case the user does not write the path of the file in exactly the same manner in both the mapping file and the package file, the distribution does not recognize it and can cause a wrong store on the target machine. COMPONENTS CHANGED OR ENHANCED: LDS.EXE LDSR.EXE PROBLEM CONCLUSION: The program flow works getting the mapping statement from the environment and they have to match esactly with the name inserted in the package file. In order to allow the match even if the two names are wriiten in a different case sequence, the code has been changed so that both the operands are trasfmormed in upper case before checking the match. PTRNBR: 1000088 APARNBR: PJ11651 PTFNBR: XR20334 EXTERNAL SYMPTOM: THE MESSAGES LDS100 AND LSR100 ARE TO BE CHANGED PROBLEM SUMMARY : The messages LDS100 and LDR100 are to be changed in order to be more undestandble in this way: LDS100 -> LDD0100 Msg file LDSDMSG.MSG not found LDR100 -> LDR0100 Msg file LDSRMSG.MSG not found COMPONENTS CHANGED OR ENHANCED: LDS.EXE LDSR.EXE PROBLEM CONCLUSION: The messages are changed as indicated. PTRNBR: 2M03755 APARNBR: PJ11651 PTFNBR: XR20334 EXTERNAL SYMPTOM: DIRTY PANEL AFTER REMOTE COMMAND BY USING LDU PROBLEM SUMMARY : Perform an external command by using LDU, invoking it with a statement of the type '* <command>', the output is redirected in a file. Anyway, if the command pops up on the screen, once it successfully ends, the main panel remains dirty showing only some characters belonging to LDU receiver panel. COMPONENTS CHANGED OR ENHANCED: LDSR.EXE PROBLEM CONCLUSION: A refresh of the receiver panel is introduced after any remote command execution and the panel should not remain dirty PTRNBR: 1000080 APARNBR: PJ11029 PTFNBR: XR20313 EXTERNAL SYMPTOM: NO ACTION FOR SOME LDU HELPS PROBLEM SUMMARY : Problem Description: No action is taken by the product when press a Keys Help with the LDU. COMPONENTS CHANGED OR ENHANCED: LDSMGR.HLP PROBLEM CONCLUSION: The source IPF file had text only for the main panel. The text related to 'keys help' is copied to any id related with KEYS HELP entry of the menu of the several panels of the LDU Manager PTRNBR: 1000081 APARNBR: PJ11029 PTFNBR: XR20313 EXTERNAL SYMPTOM: WRONG BEHAVIOR WITH LDSMGR WINDOW PROBLEM SUMMARY : When asking for a diskette driver operation and this cannot be executed, any related message is preceded by the system POP-UP. Answering the POP-UP question an user may exit from the program because of mistake. COMPONENTS CHANGED OR ENHANCED: LDSMGR.EXE PROBLEM CONCLUSION: The program already manage the return code from the operating system. Now the hard error pop-up is masked out so that the usercannotdo mistakes. PTRNBR: 1000084 APARNBR: PJ11029 PTFNBR: XR20313 EXTERNAL SYMPTOM: WRONG ERROR MSG RUNNING LDSTREE UTILITY WITH /C AND /T PARAMETER PROBLEM SUMMARY : When issuing LDSTREE command with /C and/or /T parameters, the utility does not manage correctly the command line input COMPONENTS CHANGED OR ENHANCED: LDSTREE.EXE PROBLEM CONCLUSION: The problem is due to an incorrect parsing of the input Code is changed to correctly execute its functionality. PTRNBR: A001011 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: ERROR DURING THE TC INITIALIZATION. PROBLEM SUMMARY : After an ACTIVATE operation the DosOpen of ANXSNDIR.SNA file failing with RC=32. There are the following Messages: ANX0792W ANX0763W ANX0601W ANX0613W with RC=9D00000 COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: This fix resolves also the following error messages: : ANX0792E: Error reading TC queue ANX0763E: Error TC initialization ANX0601E: Generic internal TC error ANX0612E: Dos_Create_Queue error with RC=332 ANX0613E: TC terminated with error 0100 0021 Transmission Controller tries to restart itself if it finds an error caused from previous shutdown with TC running. Sometime during second TC starting some SNA files (ANX0610E error) or System Queue (ANX0612E error) are not opened or created because they are not previously closed. With this fix, the TC closes all files and System Queue before restarting. PTRNBR: 2M02588 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: THE INFORMATIONAL MESSAGE ANXE5575 IS WRONG PROBLEM SUMMARY : Issuing an INITIATE request from the dialog, the informational message ( which appears to state that the request has been successfully submitted ) is displaied as an error message. ------------------------------------------- ERROR ANXE5575 Initiate request (s) successfully submited ------------------------------------------- Besides, the word "submited" should be changed in "submitted" COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.MSG ANXEDTMS.HLP PROBLEM CONCLUSION: In the files ANXEDTMS.MSG and ANXEDTMS.HLP has been changed ANXE5575 to ANXI5575 in order to have an Informational message. In the file ANXEDTMS.MSG I've changed "submited" to "submitted". PTRNBR: 2M02649 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: NVDM2 GETS UNRECOVERABLE ERROR WHEN OUT OF RESOURCES PROBLEM SUMMARY : If there are no enough NetBIOS resources to run the CDM LIST_WS command or when opening and refreshing the CC Domain window, an unrecoverable error was issued. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL CDM.EXE CDMD.EXE PROBLEM CONCLUSION: Now, a new message tells the user that it has to increase NetBIOS resources to list the workstations in the CC Domain. PTRNBR: 2M02664 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: ERROR ANXE5101 IF SOURCE DIR NAME IS INVALID PROBLEM SUMMARY : If from the CDM Catalog --> Build from Profile --> Build Change Profile window, in the "Source directory" field, you specify this invalid source directory name: C:-PROVA-*.* the following error message appears: Error ANXE5101 The operation failed because of an internal error. Please contact your Product Administrator. rc='0', reason='11'. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: A validation of the Source Directory has done before calling the Request Block API. PTRNBR: 2M02693 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: UNRECOVERABLE ERROR, WHEN THE WS DIR IS IN USE, DURING DELETE_WS PROBLEM SUMMARY : Attempting to delete (by a "CDM DELETEWS <workstatname>" /F) a workstation corresponding to a subdir <workstatname> in use, the NvDM/2 product get unrecoverable error while it should display an appropriate message like 'the dir <workstatname> cannot be removed'. The error message is the following: ** NetView DM/2 logged at 14:11:04 31/03/1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXEFCSD. Return codes were: Primary=13, Secondary=0, Auxiliary=0. Additional Data : 41 4e 58 45 46 43 53 44 30 30 30 31 00 00 00 00 ANXEFCSD0001.... 00 00 00 00 72 6d 64 69 72 0d 00 00 00 00 00 43 ....rmdir......C 3a 5c 4e 56 44 4d 32 5c 43 4d 52 45 51 5c 43 49 :\NVDM2\CMREQ\CI 44 43 34 30 00 00 00 00 00 00 00 00 00 00 00 00 DC40............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 ... ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ IfÍtheÍcommandÍisÍissuedÍbyÍDialogÍPanel, error message 5424 isÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ displayed (Error occurred while Deleting Workstations. See the Message Log for details). In the message log, the message 5101 appears, with rc=0 and reason=11. So also the dialog should manage, with the appropriate message the error condition. Moreover, the existing pending requests for <workstatname> workstation are not restored after the failure. That is, the CMFx.CLI, under the <workstatname> dir are deleted and not restored although the deletews command failed. COMPONENTS CHANGED OR ENHANCED: CDM.EXE ANX.MSG ANXEDTMS.MSG ANXEDTMS.HLP ANXEFAPI.DLL README.TXT PROBLEM CONCLUSION: The new ANX1043E message has been added to Command line while the ANXE5470 message and related help has been added to Dialog. More, the function files are saved under the client subdirectory if the delete_ws fails. The new messages have been added in the Readme.txt file. PTRNBR: 2M02739 APARNBR: PJ08373 PTFNBR: XR20313 EXTERNAL SYMPTOM: SYSTEM HANGS WHEN CLOSING OR EXITING CDM DIALOGS PROBLEM SUMMARY : System hangs when closing or exiting Dialogs. Running NvDM/2 v2 at XR20276 level (last CSD) with OS/2 EE 1.3 at CSD WR05050, exiting the CDM Dialogs the system and keyboard hang. It does not matter what operation has been done while in the dialog or if no operation is made: just opening the dialog and then closing it, the system hangs. To escape from the above failing event the WorkStation must be turned OFF/ON. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Corrected the handling of the product shutdown on OS/2 1.3. PTRNBR: 2M02752 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: SEND REJECTED AFTER MANY SEND REQUESTS PROBLEM SUMMARY : When there are many requests queued (about 100 send) the next one is rejected. A message appears: Send was rejected because the Transmission Controller is inactive . But the transmission controller is active. In the message.dat an error message is logged 21 times: ANX0852: (E) Too many SEND requests pending. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The code problem, it was found is in the Transmission Controller which ake in makes a mistake evaluating how many send request pending it has. The consequence was the Transmission Controller was thinking having too many send request pending if it was not really true. The bad managment of the sends pending was originated by some old send requests not properly managed by the requester so that the status of these requests remains in a not clean condition in the SNA files (ANXSNDIR.SNA). By the fix, the Transmission Controller manages in a better way the requests of sending something coming from the Agent and the user interface attempting to manage also the old pending requests. If this problem occurrs and the fix is applied, it is important to replace the SNA files with new ones: *.bak in the tcdata directory and reconfiguring the remote nodes. PTRNBR: 2M02762 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: ANXEDINI.EXE - ERROR IN STINKING HELP PROBLEM SUMMARY : When invoking Help, from ANXEDINI utility related one, for the 'Remote Destinations options', the following text is prompted: 'This is the help for this stinking panel.' COMPONENTS CHANGED OR ENHANCED: ANXEDINI.HLP PROBLEM CONCLUSION: ANXEDINI utility, related help file changed. PTRNBR: 2M02769 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: PRESSING HELP ON PENDING REQUESTS PANEL DOES NOTHING PROBLEM SUMMARY : Select 'All Pending Requests...' from the 'CDM - - Catalog' 'Engine' pulldown. When the Pending Request panel is displayed, clicking on the 'Help' button does not act nothing... no help is displayed. There should be some type of help displayed. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Problem was a missed link between the help in the .HLP file and the Pending Request dialog. To solve that, I've updated the dialogIdArray adding the dialogId of the Pending Request dialog. This dialogIdArray is then passed to the HelpManager that establishes the link with the .HLP file. PTRNBR: 2M02985 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: SAME MNEMONICS IN THE "CC DOMAIN" ACTION BAR PROBLEM SUMMARY : In the "CC Domain" window, the action bar has the same mnemonics for "Workstations" and "Windows" COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXNLS.DLL PROBLEM CONCLUSION: The following changes have been done: 1) The Workstation pull down in the CC Domain window have the mnemonic character = 'k' 2) The CC Domain item in the Windows pull down in the Remote Destinations window and in the Message Log window had before as mnemonic character 'C', but this was the mnemonic character of the Catalog item too. So,the mnemonic character, of CC Domain item, changed in 'D'. PTRNBR: 2M02994 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: RUNTIME ERRORS WHEN PRESS MORE TIME DETAILS BUTTON PROBLEM SUMMARY : If enter is All Pending Requests, then after you selected a request with the mouse and press more times the DETAILS Push Button this error Pop-Up appears: Runtime error:"asString"not understood. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The problem has been fixed by making sure that the details button cannot be pressed while we are working on the first request. PTRNBR: 2M02995 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: WRONG POP-UP IN ALL PENDING REQUESTES WINDOW PROBLEM SUMMARY : During an install command (or other CM requests), select All Pending Request, from Engine (from the Main Menu'), and then press Details; this wrong Pop-Up appears: ANXE5469 The Request Details failed because the subdirectory 'XXXXXXXX' of the Request/Reply directory cannot be found. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The problem arises when the _NdmQuery API is called (by Command Line or Dialog) while the R/R file is under the CMREQ directory and the _NdmReceive is called while the above file has been brought under the Client directory of the Agent. In this particular situation in the acRequestId field of the _NdmReceive Request Block is returned the Server name resolved and not the macro "&SERVER". When the API attempts to open the file, THE PATH IS REALLY WRONG because contains the resolved server name while the CMREQ subdirectory is "&SERVER". The load of the Server name from the Customizing Table is moved so that it's made either if the R/R file is under the «CMREQ or if it's under the «CMREQ«&SERVER directory. PTRNBR: 2M02996 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: WRONG HELP FOR THE ANXE5469 PROBLEM SUMMARY : Wrong help for the ANXE5469 Pop-Up. This Pop-Up says: ANXE5469 The Request Details failed because the subdirectory 'XXXXXXX' of the Request/Reply directory cannot be found If press HELP in this Pop-Up this no much message is displayed: 'The '%1' directory of the product Request/Reply directory cannot be found' What is '%1' meaning ? Surely, it is the directory name but in this way is not comprehensible. COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.HLP PROBLEM CONCLUSION: This problem impacted the following two Help where the '%1' has been replaced with the string 'named', in both the help messages: 1 - ANXE5469 2 - ANXE5470 PTRNBR: 2M02997 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: NO DEFINED HELP IN SOME POP-UP PROBLEM SUMMARY : In some Information Pop-Up no Help is defined. During the start of the Dialog, if the Change Controller is down, these Information Pop-Up is displayed: ANXI5195 ANXI5194 If Help is pressed, this message is displayed: 'to be defined' The above problem is common to the following messages: Numbers of messages Errors ___________________ ______ ANXI5198 Help for ANX(E)5198 To be defined ANXI5193 Help for ANX(E)5193 To be defined ANXI5199 Help for ANX(E)5199 To be defined ANXI5711 Help for ANX( )5711 To be defined ANXI5709 Help for ANX( )5709 To be defined ANXI5710 Help for ANX( )5710 To be defined ANXI5708 Help for ANX( )5708 To be defined ANXI5197 Help for ANX(E)5197 To be defined ANXI5707 Help for ANX( )5707 To be defined COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.HLP PROBLEM CONCLUSION: Helps added. PTRNBR: 2M02998 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: HELP NO COMPREHENSIBLE FOR THE ANXI5703 PROBLEM SUMMARY : During the start of the Dialog, if the Transmission Controller is down, this Information Pop-Up is displayed: ANXI5703 The Transmission Controller is in the process of being started. If press the Help Push Button this explanation is given: The operation cannot complete because Transmission Controller is busy completing a previous command The same error is present in the ANXI5704 Pop-Up. COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.HLP PROBLEM CONCLUSION: Help messages changed as follows: MESSAGE ANXI5704 ________________ Transmission Controller is in the process of being Quiesced. Help for ANXI5704 ***************** The Transmission Controller Manager is in the process of being Quiesced. You can check its status later to see if it is inactive. User response: Wait for the Transmission Controller to complete Quiescing. MESSAGE ANXI5703 ________________ Transmission Controller is in the process of being started. Help for ANXI5703 ***************** The Transmission Controller Manager is in the process of being Started. You can check its status later to see if it is active. User response: Wait for the Transmission Controller to start PTRNBR: 2M02999 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: TRAP IF IN ACTIVATE POP-UP THERE IS NO WORKSTATION PROBLEM SUMMARY : From the Main Menu press Windows then CC Domain. Before that this window is displayed with all workstations, I can press Selected then the Activate command. At this point the Activate window is open, but in the Workstation field no workstation is displayed (the field is empty). If press the Push Button 'Activate' a CDM --CC DOMAIN TRAP 000D is displayed. The module that goes in Trap is the ANXEFAPI.DLL. After that the Dialogs is closed COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXNLS.DLL PROBLEM CONCLUSION: The Activate dialog didn't disable the 'Activate' push button when the CLients list box was empty. This problem has been fixed in this dialog, and in the Delete Workstation dialog too. More, in order to avoid to have the Selected pull down enabled, when the window is opening and the clients are no in the list yet (this happens specially in the slow machines), the menu is disabled before the clients are listed. Since this behaviour could be commom to other windows, the disabling operation has bben implemented for the Selected menu of all the CDM windows. PTRNBR: 2M03001 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: UNREC. ERR FOR INSTALL ON DOS CLIENT WHEN TARG. DIR > 8 CHAR PROBLEM SUMMARY : When try to perform an install request addressed to cc dos client with a target_dir of 9 characters happens one of the following events: 1) an unrecoverable error on client, no information is logged into error.dat file, the requests aborts. 2) the request fails and the following message is logged into client message.dat file: anx0161 (e) the install request cannot be executed because the change file 'y:«......'. is invalid for the file system of the installation drive c the target_dir cut off at the 8th character is created but then not removed 3) the request fails and the following message is logged into client message.dat file: anx0266 (e) change file 'y:«........' not found even if that one exist under fsdata dir. 4) an unrecoverable error on client that logs dat on error.dat and message.dat or customized log files. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: When the unpack service is called, the target directory is create on the client machine, but in case of error no one remove it. We remove the empty directory in front of this error condition. PTRNBR: 2M03006 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: DIALOGS PREVENTS ALL MACHINE PROCESSES TO WORK PROBLEM SUMMARY : The machine hangs and no process works anymore,in a particular situation as follows: All CDM tasks are down (i.e. the Change Controller, the Transmission Controller and the Agent). Start the Dialogs with the CDMD command. During the starting the ANXI5195 and the ANXI5703 Pop-Ups are displayed. Pressing the 'Help' Push Button on the first Pop-Up and leave running this Pop-Up and its Help; wait for that the second Pop-Up appears and then press also here the 'Help' Push-Button. At this point all tasks hang and the only escape way is to turn off/on the Workstation. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The cause was the design of "modeless" message box, which has been slightly changed now. PTRNBR: 2M03055 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: MISLEADING BEHAVIOR FOR SEND CMD WITH DISTRIBUTION LIST VIA DIALOG PROBLEM SUMMARY : Not meaningful messages issued, when attempting to perform a not allowed SEND to a distribution of not homogeneous nodes, by Dialog. The following messages are logged in the Message Log window: ANXI5513 Send request(s) successfully submitted for file 'distribution list' ANX55101 The operation failed because of an internal error. Please contact your Product Administrator. rc='0',reason='6163' COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.HLP ANXEDTMS.MSG PROBLEM CONCLUSION: Added a new message to handle the 6163 return code. It says: ANXE5538 Send request failed due to an internal error, a message has been logged to MESSAGE.DAT or ERROR.DAT The message help file has been updated. PTRNBR: 2M03093 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: NO GENERAL AND KEYS HELPS IN ALL MESSAGE POP-UP PROBLEM SUMMARY : In all message Pop-Ups (Informational, Error or Warning) particular help keys are not displayed. COMPONENTS CHANGED OR ENHANCED: ANXEDTMS.HLP PROBLEM CONCLUSION: A keys help and general help dialog have been added to the help file. PTRNBR: 2M03094 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: A PANEL "RUNTIME ERROR" APPEARS WHEN THE HELP KEY IS PRESSED PROBLEM SUMMARY : Invoking CDMD when the Dialog is already started, the correct panel "CDM dialog already started" is displayed, but pressing on the Help button a wrong panel appears such as: ---------------------------------------- Ù Runtime error: Ù Ù "HelpPanelForErrorNo:" not understood. Ù ---------------------------------------- COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Create help instance before any message box is displayed. PTRNBR: 2M03120 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: IN MORE HELP MESSAGES OF ANXEDINI UTILITY THE DEFAULT DIR IS WRONG PROBLEM SUMMARY : In more Help messages (see for example FSDATA dir, SHARED Dirs..) of ANXEDINI utility the default directory is wrong, it's D:«IBMANX22 instaed of BootDrive«IBMNVDM2. COMPONENTS CHANGED OR ENHANCED: ANXEDINI.HLP PROBLEM CONCLUSION: Changed dialogs and documentation in accordance. PTRNBR: 2M03123 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: MISSING A ERR MSG WHEN THE EXTERNAL INSTALL GIVES RC>0 PROBLEM SUMMARY : The following message: anx0253 (e): the external program '......' failed with exit code '....' is not logged when the failed external program is submitted by an external install request, as instead happens for initiate. Only the following one is logged: anx0225 (e): the processing of the install request on workstation for an object with global name '....' was unsuccessfully executed by the ................. COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE PROBLEM CONCLUSION: The module ANXCCPEI (External Install main) manages some codes returned from an external program and issues the proper messages in these cases. When an external program ends with an unexpected code the failure message is too generic. We set the correct message ANX0253 in these cases, but we don't modify the special error cases already managed by the module. PTRNBR: 2M03140 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: FAILURE OF A LARGE FILE TRANSMISSION PROBLEM SUMMARY : It is not possible to SEND from host a resource of 162 Mbytes. After having transmitted about 150 Mbytes, the TC terminates because of error. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The ERROR.DAT for this problem shows an error return code = d6 that means Too_many_module from DosLoadModule call. ** NetView DM/2 logged at 22.26.52 18.05.1993 ** Error detected in NetView DM/2 DS component. The error was generated in module TCSHELL . Additional Data : 54 43 53 48 45 4c 4c 20 30 30 30 38 70 07 00 02 01 01 d6 00 The problem was generated because a large number of DosLoadModul is done. In fact when TC starting it loads the Specific Server DLL. The Transmission Controller, to store a file, must to call the loaded Specf Server each 4k bytes of data arriving from the partner node. For a programming error, each time that the Transmission Controller calls Specf Server to store data, it loads the Specf Server. Even if the TC checks if the Specf Server is loaded, the test fails because the variable tested is always 0. The fix is to declare as STATIC the tested variable so the Transmission Controller loads the Specific Server only at start time. Also the performance improving. PTRNBR: 2M03145 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: AT DATA TRANSMISSION SYSTEM STOPS PROBLEM SUMMARY : After the transmission of a lot of resources (about 100 resources) the transmission stops after the ANX0082, ANX0074, ANX0051 messages appear. The error log shows a failure of ANXBCP40 calling ANXCSCD4 (update service) module. ANXCSCD2 module fails with SQLCODE 0afeffff. The error log is the following: ** NetView DM/2 logged at 08:37:32 (AM) 09-01-1993 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXBCP40. Additional Data : 41 4e 58 42 43 50 34 30 30 30 30 34 94 06 00 08 ANXBCP400004.... 41 4e 58 43 53 30 44 42 41 4e 58 42 43 50 34 30 ANXCS0DBANXBCP40 41 4e 58 43 53 43 44 34 10 00 14 00 0a fe ff ff ANXCSCD4.....].. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 02 00 4d 53 49 37 20 20 20 20 20 20 20 20 ....MSI7 20 20 20 20 4c 41 42 4f 52 20 20 20 20 20 20 20 LABOR 20 20 20 20 4a 4f 42 44 41 54 20 20 20 20 20 20 JOBDAT 20 20 20 20 50 52 4f 43 20 20 20 20 20 20 20 20 PROC 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 90 90 90 00 00 00 00 00 00 10 50 .ˆˆˆ.......P 00 00 43 3a 5c 49 42 4d 4e 56 44 4d 32 5c 46 53 ..C:\IBMNVDM2\FS 44 41 54 41 5c 46 53 46 30 30 30 30 39 00 00 00 DATA\FSF00009... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 .... COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL ANXDBCLI.DLL ANXCSCD4.BND PROBLEM CONCLUSION: In the ANXCSCD4 catalog services module, the cursor was not closed after the last fetch: now, the cursor is closed. PTRNBR: 2M03167 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: An unexpected and meaningless message is issued after messages ANX1552 and ANX1554. PROBLEM SUMMARY : After a NetBIOS error during the initialization of the ANXCMLDR.COM module two messages ANX1554 and ANX1552 are correctly issued. Subsequently a third unexpected message with no message number is displayed: "The CDM Agent is already started". COMPONENTS CHANGED OR ENHANCED: ANXCMLDR.COM PROBLEM CONCLUSION: The message has been removed. PTRNBR: 2M03172 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: ANXEFAPI REQUIRES NETBIOS IN HOST ATTACHED WORKSTATION (Q3) PROBLEM SUMMARY : When CSD XR20276 or XR20302 is applied on a product installed as host-attached workstation (no CC Server function), NETBIOS DLLs were a pre-requisite even if that workstation does not use any NetBIOS application. If NetBIOS is not installed, neither commands nor dialog can be used. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: NetBIOS is no more a pre-requisite for using the external interface of NetView DM/2 when installed as host-attached workstation. PTRNBR: 2M03178 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: CDM CANNOT LOAD CUST.TABLE IF SEMAPHORE OWNER DIED PROBLEM SUMMARY : In some strange situations, when transmission controller dies, is not possible to issue a CDM command. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: This is due to the fact that ANXCRPG6 tries to open the Customizing Table Semaphore and the return code of DosSemRequest is ERROR_OWNER_DIED, so it logs an error. Changed ANXCRPG6 module. PTRNBR: 2M03180 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: OS/2 CC Client Installation - 5" Package: wrong informational message PROBLEM SUMMARY : When installing OS/2 CC Client via PM, after inserting the 11th diskette (5" package), the message: "Processing Diskette 12" is displayed on the installation dialog. COMPONENTS CHANGED OR ENHANCED: The component affected by the change is the OS/2 CC Client installation body (5" package) for PM (PMBODY.EXE). PROBLEM CONCLUSION: The diskette counter has been initialized to 11 instead of 12. PTRNBR: 2M03185 APARNBR: PJ11018 PTFNBR: XR20313 EXTERNAL SYMPTOM: CDM AGENT FAILS WITH ANX0211 INSTALLING RELDATA PROBLEM SUMMARY : If a user tries to install a reldata object having the database table qualifier with 8 or more characters, the install fails with ANX0211 error. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The parsing table algorithm has been corrected to manage also the error occurrence PTRNBR: 2M03188 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: 100C 0001 TRANSMISSION CONTROLLER ERROR PROBLEM SUMMARY : When the node receives a MU from Host, normally the MU status progression is: NOT_RECEIVED, IN_TRANSIT, COMPLETED, PURGED. In this scenario, for a previous error sequence, the status at the node for the arriving MU is PURGE. The TC Receiver Manager puts a CRMU into the CRMU Queue to communicate later this PURGED status to the Host and issues a Receive_and_Waits APPC verb to obtain a new MU (the node waits a DTMU). The Host continues to send the second buffer of previously DTMU. The node receives this buffer and interprets the first 4 bytes as length an MU Id of the new DTMU. This creates the 100C 0001 error. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: In this scenario when the Receiver Manager finds a MU in PURGED status, it issues a SEND_ERROR APPC verb and puts a CRMU into the CRMU queue to communicate to the Host the MU PURGED status. The node deallocates the conversation. PTRNBR: 2M03190 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: IT IS NEED TO SPECIFY WHAT IS THE 5 " INST. DISK. PROBLEM SUMMARY : The nvdmpms.exe file is on the second diskette of the 5" package. The documentation does not tell that for the server installation by presentation manager the installation diskette is the second of the 5" package. COMPONENTS CHANGED OR ENHANCED: README.TXT PROBLEM CONCLUSION: Changed documentation. PTRNBR: 2M03233 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: Boot Diskette Updating Program: change target directory reference from IBMANX to IBMNVDM2 Ref. PMR 5X061 PROBLEM SUMMARY : The boot diskette updating program must load pristine agent code under IBMNVDM2 target directory on boot diskette, as described in documentation material. COMPONENTS CHANGED OR ENHANCED: The component affected by the change is the Boot Diskette Updating Program (NVDMBDSK.EXE). PROBLEM CONCLUSION: The boot diskette updating program will create the target directory on the boot diskette, naming it IBMNVDM2; moreover, to avoid the lack of space on disk and config.sys errors at pristine startup, any reference to the old target directory name has been removed from boot diskette. PTRNBR: 2M03257 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: SOME CMDS CLOSE CATALOG EVEN IF THEY DO NOT OPEN PROBLEM SUMMARY : Some commands (such as CDM STOP, QUERY_CF ) invoke the Database Manager to close the NetView DM/2 Catalog even if it has been never opened by that command; COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Those command do not try to close the NetView DM/2 Catalog if they never opened it. PTRNBR: 2M03268 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: CDM SHUTDOWN HANGS ON LAN HOST ATTACHED ENVIRONMENT PROBLEM DESCRIPTION: Performing the CDM SHUTDOWN command in an environment with the TC component ( Different from Stand-Alone LAN) the Command line doesn't Return the prompt back. The CDM.EXE, ANXCMSRV.EXE ANXSNADS.EXE result hanging during the closing process. EXECUTABLE MODULES CHANGED OR ENHANCED: ANXEFAPI.DLL (ANXEFQ3S.DLL, ANXEFQ4S.DLL) ANXCMSRV.EXE PROBLEM CONCLUSION: The Problem was due to a bug in the synchronization mechanism between the External User Interface and Change Controller Component. PTRNBR: 2M03293 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: UNRECOVERABLE ERROR IN BUILD WITH &+TOKEN PROBLEM SUMMARY : If in the Build profile the tokens with "&" are used but one of them is incorrect (for example Global Name = "config.sys.&netid.&xxxxxx"), the CDM BUILD command returns the message ANX0211 (unrecoverable error). COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The _NdmBuild API in the module ANXEFCBL.C was modified. An error return code, returned by the function AnxGlbNmeQTknAttr about an invalid token in the GlobalName, was managed as an unexpented condition. The error code by that functions is now correctely managed. PTRNBR: 2M03294 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: WRONG DOCUMENTED CDM MESSAGE EXIT ROUTINE PROBLEM DESCRIPTION: The ANXLUSER.DLL, shipped as an example for the customizable CDM user exit routine, has documented with errors. In fact, there is an inversion of the parameter passed to the ANXLUSER that prevent the user to write its own routine. EXECUTABLE MODULES CHANGED OR ENHANCED: README.TXT PROBLEM CONCLUSION: The ANXLUSER.C file documented in the Installation and Customization Guide" at page 174 has been corrected. Moreover it was produced another sample of ANXLUSER.C that is embodied in the README.TXT distributed with this CSD. This sample of ANXLUSER.DLL Logs in a user's Message Log the Message and print also all the variable of the message. PTRNBR: 2M03347 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: PMR 0108X : CDM STOP HANGS ON Q4 ENVIRONMENT PROBLEM SUMMARY : When performing CDM STOP command can happen the command does not give back control to the command line and the prompt does not appear any more on the full screen. NvDM/2 does not really stop. The Transmission Controller entry remains in the OS/2 task list&/ If the CDM STATUS command is issued from another OS/2 screen, all NvDM/2 modules are still in active or terminating status. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The hang condition in T.C could happen also in processing a CDM SHUTDOWN command. This is due to the fact that changed code in ANXSNADS.EXE is involved each time it is requested to end the Transmission Controller: this fix also solves this situation. PTRNBR: 2M03348 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: CID: RC=1608 WHEN DATABASE IS NOT LOGGED ON PROBLEM SUMMARY : When doing a redirected install of the Server component of NVDM/2, if the database is not logged on that the installation, getting return return code 0x1608 which is an non-architected CID return code. COMPONENTS CHANGED OR ENHANCED: - All installation programs: 1- nvdmclt 2- nvdmirec 3- nvdmpmc 4- nvdmpms 5- nvdmepms 6- nvdmeins 7- nvdminst 8- nvdmcopy 9- nvdmecpy 10 -body.exe 11 -pmbody.exe 12 -sbody.exe 13- pmsbody.exe PROBLEM CONCLUSION: Now in case of a "Incorretc Environment" condition, the exit code will be 1604 (Unexpected Condition). PTRNBR: 2M03358 APARNBR: PJ09719 PTFNBR: XR20313 EXTERNAL SYMPTOM: RETRIEVE OF LOGFILES FAILS IF THE LOGFILE HAS BEEN CHANGED PROBLEM SUMMARY : The problem arose when the a CID application, invoked from NvDM2, failed doubly. In fact, the first time a log file was created and the relative entry was inserted in the catalog so the host was able to retrieve it, the second time a new log file was created but we used the entry previously inserted in the catalog. In this way the host tried to retrieve the log but the operation failed because the time specified in the catalog for the log file was different from that one real. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Whenever a log file is created the old entry is deleted and a new entry is inserted in the catalog. PTRNBR: 2M03363 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: TRANSMISSION RESTARTABILITY FAILURE PROBLEM SUMMARY : When a resource is cataloged and compressed (using NVDMLZW algorithm) and is sent at the destination (no difference if the send is executed from host to node or form node to node) the resource arrives, but is not decompressed if a line failure occurred during the transmission. The decompression action at node fails. More, if a /TXT is cataloged at source and is sent, the server ends at the target node, if a line failure occurred. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: When there is a line failure during a transmission, the specific server saves informations in the check point file ((anxbi1ck layout) (nvdm2cks file)) to restart correctly. If the operation is invoked from host, and the replace option is specified, the the specific server is invoked with exception action abend, but the specific server instructions are not saved in the check point file, erro- neously, so when the specific server restarts doens't work correctly. others informations that are not in the check point record are: record format, used for txt file algorithm name and parameters ccsid description text ccsid description text string The fields for record format and for specific server instruction are not present also in the operation control block. This missing fields give problem in some others restart cases. The fields have been inserted in the control blocks, and these informations are managed correctly between operation control block and check point file and between specific server and transform handler. PTRNBR: 2M03375 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: The Exit Code "0004" "0008" and "0012" are considered error exit code PROBLEM DESCRIPTION: The CM/2 that is using this return code to report a successful termination with some warning message ends unsuccessful for NetView DM/2 EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: Now the NetView DM/2 support these new CID exit code PTRNBR: 2M03385 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: ACTIVATE CAN TAKE 10-15 MINUTES PROBLEM DESCRIPTION: Sometime it was noticed that the activate can take 10-15 minutes, other times it works fine. After about 1.5 minutes the Transmission controller ends, but the Change Controller remains "terminating". Then 10-15 minutes later the node IPL's. EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: The pre-IPL sequence was modified to avoid this deadlock situation. PTRNBR: 2M03388 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: MSG ANX0029 issued at CDM SATRT AGENT PROBLEM DESCRIPTION: At CDM START command the CDM AGENT goes INACTIVE and the message ANX0029 is issued twice. Changing the LogOption from NVDM to COMM the following error is logged: Additional Data: 414E584343504D4D3030303488010008414E584353304642 ANXCCPMM0004..ANXCS0FB 414E584343504D4D414E58435350463010000800040073A5 ANXCCPMMANXCSPF0...... 0000000000434D4630303030312E434C4900000000000000 CMF00001.CLI.......... 000... EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE ANXCMCLP.EXE PROBLEM CONCLUSION: The problem occurs when later a reboot, upon an Activate, the IBMNVDM2.SAV file is deleted before the CDM Start command. This cause a Loop on the request that cause the TOO_MANY_OPEN_FILES condition detected and reported in the Error Log. PTRNBR: 2M03395 APARNBR: PJ09676 PTFNBR: XR20313 EXTERNAL SYMPTOM: CHANGE RETRY NUMBER FOR CONVERSATION ATTEMPTS PROBLEM SUMMARY : Actually, after a "retriable" conversation failure APPC code 0003 0005 the number of re-attempts is 5 (every 10 minutes). This is changed in order to re-attempt the conversation indefinitively. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: When Transmission Controller receives an APPC retry error, it retries the APPC operation indefinitely, until problem fixed. PTRNBR: 2M03468 APARNBR: PJ11033 PTFNBR: XR20313 PROBLEM ABSTRACT: ABEND DURING UNSUCCESSFUL INSTALL IN SERVICE WITH REMOVABILITY YES PROBLEM DESCRIPTION: If an error occurs, processing the Section Install of a change file (a program error for example) where a FileSpecList Section is defined, and the Install is Removable in Service or Trial area the CDM Agent goes down with MSG ANX00279 and no Error Log. EXECUTABLE MODULES CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: An error has been found during the AutoRemove process of the FileSpecList files already installed when the error take place in the Install Section: problem fixed. PTRNBR: 2M03490 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: GMT MISSING IN RRMU PROBLEM SUMMARY : Inconsistencies in the SNA/DS inplemented architecture. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: In the SNA/DS architecture the minimum RRMU length is 21 bytes. In the RRMU encoded by Send_Manager at NvDM/2 node this length is 20 bytes. The RRMU has the minimum length when the time is GMT so no offset is required. In this case the 21-byte is the GMT flag set to X'E9' missing in the previous RRMU. PTRNBR: 2M03502 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: PMR 24213 : T.C. DOES NOT PROCESS EXTERNAL REQUESTS PROBLEM SUMMARY : In very randomly circumstances the Transmission Controller is not ever able to process requests coming from other NvDM/2 components, from the external interface or other partner nodes. The CDM STOP command is not able to stop it. If the CDM STATUS command is issued the Transmission Controller is still active. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: Changed an internal Transmission Controller timeout. PTRNBR: 2M03525 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: 'TO_BE_DELETED' AND 'DELETED' ARE MUTUALLY EXCLUSIVE PROBLEM SUMMARY : SNA/FS inconsistencies in the error response that nvdm2 send to any partner as a result of a remote delete command. The file we try to delete does not exist in the target system and NVDM2 is returning the TO_BE_DELETED_NAME and the DELETED_NAME (both). It should return the TO_BE_DELETED only because no file was deleted (to_be_deleted_name & deleted_name are mutually exclusive). COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: Into the Specific Server report the following fields are now encoded in mutually exclusive way: To_Be_Fetched with Fetched To_Be_Deleted with Deleted To_Be_Stored with Stored NOTE: In a DELETE operation the Specific Server returns DELETED token string in the Report when the object to deleted is not found. PTRNBR: 2M03527 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: PMR4096X: CHECK DRIVE DURING NVDMECPY PROBLEM SUMMARY : All the installation programs,before this fix,verified that all the drives attached at the workstation were not damaged. COMPONENTS CHANGED OR ENHANCED: - All installation programs: 1- nvdmclt 2- nvdmirec 3- nvdmpmc 4- nvdmpms 5- nvdmepms 6- nvdmeins 7- nvdminst 8- nvdmcopy 9- nvdmecpy 10 -body.exe 11 -pmbody.exe 12 -sbody.exe 13- pmsbody.exe PROBLEM CONCLUSION: Now the test is done just on the involved drives PTRNBR: 2M03615 APARNBR: PJ10743 PTFNBR: XR20313 EXTERNAL SYMPTOM: SEND NOT EXECUTED FOR FILE WITH EXTENDED ATTRIBUTES PROBLEM SUMMARY : This problem occurs only with Japan Data Base. 1) CATALOG a resource with local name with Extended Attributes. Into the FS Catalog we have for Software Object Type: 1 char ========> (10)x 2 char ========> (30)x 2) SEND the resource. Into the FS Catalog we have for Software Object Type: 1 char ========> (10)x 2 char ========> (30)x 3 char ========> (E4)x means Extended Attributes in local file 4 char ========> (E4)x means Extended Attributes in local file In Japan DB the Extended Attributes values (E4, E4) are written in DBCS. The operation ended successfully. 3) SEND the same resource. The Specific Server searches the resource into the FS Catalog specifying the Global Name and Object Type like search key. The operation ended unsuccessfully because the resource is not found. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL ANXBFTH.DLL PROBLEM CONCLUSION: In a Send operation the Object Type is set to '?' '?' '?' '?'. It means that the Object Type is not a key for the searching catalog entry. A different Object Type setting is performed during a Retrieve operation (for this reason the Object Type is defined like a key). '?' is a wild char for a single character, but in the Japan FS Catalog (E4)x is a part of a double byte. So the search of entry in the Catalog fails if the resource has the Extended attributes specified. The solution is to change '?' in '*' for the EA Object Type. This allowed to ignore the Extended Attributes in the Object type search key. PTRNBR: 2M03625 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: PMR 2X982 T.C_DOES NOT LOG AN ERROR.DAT MESSAGE PROBLEM SUMMARY : When T.C. has to log the,into error.dat, an error such as: 4c53445253304c4d30303038446f7353 LSDRS0LM0008DosS 656172636850617468 earchPath it is not able to log the real error cause. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: In order to improve the ERROR LOG reading, a new data is added in the ERROR LOG. This data will show the DosSearhPath return code to better understand the real error cause. PTRNBR: 2M03626 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: APPCWAIT DOES NOT WAIT FOR ENOUGH TIME PROBLEM SUMMARY : APPCWAIT function does not wait enough time for the APPC coming up. This means that in the startup.cmd, when APPCWAIT gives back the control and it is immediately executed CDM START, NvDM/2 is not able to stay on because it finds the APPC still off. This problem refers to a customer PMR: 4131X. In the Customer Communication Manager environment the maximum wait timeout value in APPCWAIT function is not enough to wait for the interval time Comm.Mgr spends to start APPC. COMPONENTS CHANGED OR ENHANCED: APPCWAIT.EXE PROBLEM CONCLUSION: APPCWAIT stop the execution of STARTUP.CMD for 5 minutes or until the APPC is up. PTRNBR: 2M03628 APARNBR: PJ11033 PTFNBR: XR20313 EXTERNAL SYMPTOM: T.C. PATH MUST BE INSERTED IN DPATH OF CONFIG.SYS FILE PROBLEM SUMMARY : <TargetDir>«TCDATA must be insered in the DPATH COMPONENTS CHANGED OR ENHANCED: 1- PMSBODY.EXE 2- SBODY.EXE PROBLEM CONCLUSION: <TargetDir>«TCDATA is now insered in the DPATH statement. PTRNBR: 2M02699 APARNBR: PJ08268 PTFNBR: XR20302 EXTERNAL SYMPTOM: ACTIVATE FAILURE WHEN LOCKUP IS ACTIVE ON PS2 PROBLEM SUMMARY: Submitting an ACTIVATE plan on a workstation where the LOCKUP is active, the function is not executed until the user types the password on the machine. COMPONENT: ANXBASE.DLL PROBLEM CONCLUSION: A new managing of VioPopUp (OS/2 API routine ) has been inserted in the ANXCRPH0 module Now the VioPopUp function try to obtain the screen , in order to display the message, for 3 times. If the VioPopUp fails, the following actions will be taken: - a warning Beep will be issued, one for each attempt to obtain the screen. - no messages will be displayed and the normal flow of operation will be continued. - a final warning Beep will be issued to advise the user that the process goes ahead. The proposed fix will work for OS/2 2.0 while for OS/2 1.3 requires CSD XR05150 that changes the Lockup behaviour. Also this requirement should be highlighted to the user. PTRNBR: 2M02658 APARNBR: PJ08273 PTFNBR: XR20302 EXTERNAL SYMPTOM: DIALOG TRAPS IF CM/2 LOG FORMATTER IS OPENED PROBLEM SUMMARY: This abnormal behaviour was discovered during system test of CM/2 in Raleigh but it has been reproduced also in Rome. ENVIRONMENT: OS/2 2.0 (no Service Pak) CM/2 1.0 SCENARIO OF THE EVENT: The CMD Manager and Agent are active; the Dialog is opened. Click on icon of "Log Formatter inside FFST/2 folder". Choose the lof file to display (the only selectable file in the current directory). As soon as the window to display the log is opened, the CDM catalog window traps. The trap info are: CDMD.EXE PWMWIN.DLL 0001 P1=0000008 P2=0000aa1c EAX=7b200158 EBX=00002c90 ECX=0 EDX=0 ESI=000004A8 EDI=0000AA27 DS=0000 (in Rome) DS=d14f DSACC=00f3 DSLIM = 0000a537 (in Raleigh) ES=0000 (in Rome) ES=b93f ESACC=00f2 DSLIM = 00006FFF (in Raleigh) FS=150b FSACC=00f2 FSLIM=00000030 GS=150b GSACC=00f1 GSLIM=00000023 CS:EIP=dodf:00022b3 CSACC=00ff CSLIM=0000eea1 SS:ESP=002f:00004db6 SSACC=00f3 SSLIM=00004e1f COMPONENT: CDMD.DLL FCLDLGP.DLL FCLDRCP.DLL PROBLEM CONCLUSION: It was found that a window was not destroyed and is causing the trap: code changed to destroy this window. PTRNBR: 2M02739 APARNBR: PJ08373 PTFNBR: XR20302 EXTERNAL SYMPTOM: SYSTEM HANGS WHEN CLOSING OR EXITING CDM DIALOGS PROBLEM SUMMARY: System hangs when closing or exiting Dialogs. Running NvDM/2 v2 at XR20276 level (last CSD) with OS/2 EE 1.3 at CSD WR05050, exiting the CDM Dialogs the system and keyboard hang. It does not matter what operation has been done while in the dialog, or if no operation is made. Just opening the dialog and then closing it, the system hangs. It is necessary to reboot to recover the situation. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: Code changed to handle correctly product shutdown on OS/2 1.3. PTRNBR: 2M02934 APARNBR: PJ08590 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG MAX RECORD LENGTH FIELD SET IN CATALOG FUNCT. PROBLEM DESCRIPTION A Transform Handler routine computes the max record length of a text file analyzing the '0A' hexadecimal character occurrences. In fact the '0A'x character (LF) delimited all records of the text file so it will be possible to find the max record length. The Transform Handler routine searches the '0A'x character using the 'strchr' function. This function ends to scan the input buffer when it finds '00'x character (/0) that the routine put at the end of the input buffer. A text file (a file created with the usual editors) doesn't contain the '00'x character so the routine works well. If the user creates a text file with '00'x character in the body of file (like in this PTR) the searching of '0A'x character can fail. COMPONENT: ANXBFTH.DLL PROBLEM CONCLUSION: The 'strchr' function (to find '0A'x char) is changed with a searching routine. It doesn't need an '00'x character at the end of buffer. PTRNBR: 2M02670 APARNBR: PJ08652 PTFNBR: XR20302 EXTERNAL SYMPTOM: A TRAP D OCCURS WITH ANY,TC RELATED COMMANDS PROBLEM SUMMARY: On a PS/2 with OS/2 1.3.2 5150 EE, it is not possible to work with NetView DM/2 2.0, because with any commands a trap occurs. COMPONENT: ANXSNADA.DLL PROBLEM CONCLUSION: The provided fix addresses two problems causing the TRAP D. The first one was about a managment of a particular OS/2 return code provided by the OS/2 DosSubAlloc function in the involved OS/2 release. The second problem was a bad managment of memory areas to log ment of error messages by the ANXSNADA.DLL. h caused PTRNBR: A001011 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: STW SEVERN - ERROR DURING THE TC INITIALIZATION. PROBLEM SUMMARY: The Transmission Controller tries to restart itself if it finds an error caused from previous shutdown with TC running. Sometime during second TC starting some SNA files or System Queue cannot be opened or created because they have not been previously closed. COMPONENT: ANXSNADS.EXE PROBLEM CONCLUSION: Before restarting TC, all files and System Queue are closed. PTRNBR: A001015 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SYSABEND 2 AFTER AN ACTIVATE PROBLEM SUMMARY: Sometimes in case of TRAP the message SYABEND 2 is issued and there is no way to get the TRAP information. COMPONENT: ANXBASE.DLL PROBLEM CONCLUSION: Now the TRAP is showed in the normal OS/2 Black panel. PTRNBR: 1000070 APARNBR: PJ08760 PTFNBR: XR20302 EXTERNAL SYMPTOM: PROBLEMS OCCUR WHEN THE DISTRIBUTOR NAME IS DUPL. IN THE LAN PROBLEM SUMMARY: In a distributor machine when a Distributor name used by another workstation (for ex. by a NetViewDM/2 Client) is defined, the start of LDS program fails because the LDU is not able to uplaod the distributor name. If I try to change this name the LDU fails because the NetBios resources are not enough. The only way to continue is re_ipl the machine. COMPONENT: LDS.EXE PROBLEM CONCLUSION: The Ldu Distributor ends freeing the NetBIOS resources but in some cases this operation has not been correctly executed. Now any time the distributor ends it frees the resources, either in a normal end or in case of an error exit. PTRNBR: 1000076 APARNBR: PJ08760 PTFNBR: XR20302 EXTERNAL SYMPTOM: UTILITY LDSTREE TO BE IMPROVED PROBLEM SUMMARY: The utility LDSTREE should be improved to take care of: A) the hpfs possibility to write files and directories in lower case B)the need od customer to have a tool to write distributor mapping files quickly COMPONENT: LDSTREE.EXE LDAMSG.MSG PROBLEM CONCLUSION: The utility has been improved to take care of the sugggested items. LDSTREE is now a utility to help to create package or distributor mapping file The syntax for LDSTREE is now: LDSTREE -pathname- -/C- -/M- -/D- -/R- -/T:targetdir- -pathname- : any valid pathname on the system. 'C:\' is the default. -/C- : the output will be a case sensitive copy of the directories on the distributor. -/M- : make directories. A 'create directory' command will be inserted for each directory. -/D- : delete all files. An 'erase file' command will be inserted to delete all files in all directories. -/R- : remove directories. A 'delete directory' command will be inserted for each directory in reverse order at the top -/T:targetdir- : the entire tree having as root the -pathname- will be remapped to a tree having as root the -targetdir- If /T is specified /D /M /R will be ignored and only the map will be the output If /R is specified /D will be ignored. The output will be the standard output (usually the screen) unless an output redirection will be done. PTRNBR: 2M02588 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE INFORMATIONAL MESSAGE ANXE5575 IS WRONG PROBLEM SUMMARY: Issuing an INITIATE request from the dialog, the informational message ( which appears to state that the request has been successfully submitted ) is displaied as an error message. ------------------------------------------- ERROR ANXE5575 Initiate request (s) successfully submited ------------------------------------------- Besides, the word "submited" should be changed in "submitted" COMPONENT: ANXEDTMS.MSG ANXEDTMS.HLP PROBLEM CONCLUSION: In the files ANXEDTMS.MSG and ANXEDTMS.HLP have been changed messages ANXE5575 to ANXI5575 in order to have an Informational message. In the file ANXEDTMS.MSG has been changed "submited" to "submitted". PTRNBR: 2M02589 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE FIELD "PARAMETERS" IN THE DETAILS WINDOW IS DIRTY PROBLEM SUMMARY: A minor problem has been detected issuing two subsquent INITIATE requests, the first one with parameters and the second one without parameters but scheduled. Then, if I choose "ENGINE - All pending requests .." to check the status of the issued requests and, for the second one (without parms) I push on the "Details" buttom, the field "parameters" contains binary characters. This isn't a processing problem because the second request is anyway successfully executed. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: The CDMD.EXE took off the binary characters(or any other bad character) from the 'parameters' field. A new method it's used in order to output the parameters string at soon it finds a character with ascii value equal to 0. PTRNBR: 2M02595 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SNA ARCHITECTURE INCONSISTENCIES IN SPECIFIC SERVER PROBLEM SUMMARY: In the specific server code, according to future product enhancements, there are some inconsistencies versus the sna architecture. this inconsistencies impacts the structure of the mu that is created by specific server and then sent thru the sna network. COMPONENT: ANXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: Changed code to remove/prevent inconsistencies versus SNA architecture. PTRNBR: 2M02638 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG BEHAVIOUR IF SEND HAS REPLACE OPTION PROBLEM SUMMARY: When the specific server must replace a object with the last token '&datetime': 1)if the object passes the control on the token attributes the last token of the to be stored token string is not substituted with the token '&datetime', so a entry with only the last token different is created. 2)the object doesn' pass the control on the token attri- butes, but the error in wrongly managed. COMPONENT: ANXBFTH.DLL ANXLBFS.DLL PROBLEM CONCLUSION: When the user invokes a send with replace option and the object to replace has the token '&datetime', this must be replaced only if the the object sent has the last token with attributes numeric ordered. PTRNBR: 2M02649 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: LISTWS GETS UNRECOVERABLE ERROR WHEN OUT OF RESOURCES PROBLEM SUMMARY: Doing a LISTWS command or opening the the CC Domain window from CDM Dialog, you have a message telling "An unrecoverable error occurred" when there are not enough NetBIOS resources COMPONENT: ANXEFAPI.DLL CDM.EXE ANX.MSG PROBLEM CONCLUSION: A new message is issued telling that the problems is due to lack of NetBIOS resources. Search in README.TXT for a table of required NetBIOS resources PTRNBR: 2M02657 APARNBR: PJ08760 PTFNBR: XR20302 EXTERNAL SYMPTOM: LDUSEED UTILITY WRONG BEHAVIOUR UNDER OPER. SYSTEMS STEM DIFFERENT THAN ENGLISH/AMERICAN VERSION PROBLEM SUMMARY: The Lduseed utility created for its use a config.sys that did not take care about the different country parameter of the config.sys in the Installation diskette. COMPONENT: LDUSEED.EXE LDUDISK.EXE PROBLEM CONCLUSION: Now the code is changed so that the final config.sys is only a modified version of the installation diskette config.sys. In this way it should be mantained even the load to any needed device driver or dll to the NLS different versions PTRNBR: 2M02664 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ERROR ANXE5101 IF SOURCE DIR NAME IS INVALID PROBLEM SUMMARY: If from the CDM Catalog --> Build from Profile --> Build Change Profile window, in the "Source directory" field, you specify this invalid source directory name: C:«SAMPLE«*.* the following error message appears: Error ANXE5101 The operation failed because of an internal error. Please contact your Product Administrator. rc='0', reason='11'. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: A validation of the Source Directory has done before calling the Request Block API. PTRNBR: 2M02665 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INSTALLATION MESSAGES ARE NOT ALIGNED WITH MANUALS PROBLEM SUMMARY: The messages contained in the installation manuals were not aligned with the messages displayed and logged by the installation procedures. COMPONENT: For the entry package: NVDMEINS.EXE SBODY.EXE NVDMECPY.EXE NVDMEPMS.EXE PMSBODY.EXE NVDMIREC.EXE For the extended package: NVDMINST.EXE SBODY.EXE NVDMCOPY.EXE NVDMPMS.EXE PMSBODY.EXE NVDMIREC.EXE NVDMCLT.EXE BODY.EXE NVDMPMC.EXE PMBODY.EXE PROBLEM CONCLUSION: Missing messages have been added in the manuals and corrections have been made when necessary. Only error and warning messages will be contained in the manuals, because informational messages are displayed and logged without the message number, so it's no possible to reference them in the manual; however informational messages are self explaining. PTRNBR: 2M02691 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: BUILD CHANGE FILE WITH SOURCE DIR ON MORE DISKETTES PROBLEM SUMMARY: It is impossible build a change file with source on more diskettes. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: When the Find Files dialog is displayed, the current directory is no more changed to the source directory: in this way, we don't have anymore problem to read files from diskettes. PTRNBR: 2M02693 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: UNRECOVERABLE ERROR WHEN DELETE_WS WITH THIS WS DIR IS IN USE PROBLEM SUMMARY: In module ANXEFCSD function RemoveAllDir when rmdir() was called, errno = 13 was not managed. COMPONENT: CDM.EXE CDMD.EXE ANXEFAPI.DLL PROBLEM CONCLUSION: Now a new message is displayed instead of the 211 (unrecoverable error). PTRNBR: 2M02716 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG MANAGEMENT OF RETURN CODES IN THE NVDMUPD UTILITY PROBLEM SUMMARY: When run the NVDMUPD utility through an external install with a syntax mistake in the change profile, a wrong message appears. COMPONENT: ANXH.MSG PROBLEM CONCLUSION: The message ANX1305 has been added. PTRNBR: 2M02724 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: UNRECOVERABLE ERROR WHEN DELETING WORKSTATIONS PROBLEM SUMMARY: In ANXEFCD0 when the function CheckRequest is called, the RC variable must be set to UNEXPECTED_CONDITION after calling AnxError1Log. The same problem occurs in ANXEFCC0.C module. COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: Now in the error log the right return code is displayed. PTRNBR: 2M02731 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: NVDMRCSD AND NVDMPCSD UTILITIES MIS-PROCESSING PROBLEM SUMMARY: The two utilities NVDMR(P)CSD, used to distribute the CSD, had problems in maintenance situation. COMPONENT: NVDMPCSD.EXE NVDMRCSD.EXE PROBLEM CONCLUSION: The log of the two utilities was enhanced. A bug on FAT file-system (in particular situations) was fixed. In case of boot-intallation of the CSD, a multilog is done in every OS/2 bootable drive. PTRNBR: 2M02750 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PRODUCT VERSION REFERENCES ARE INCONGRUENT PROBLEM SUMMARY: Product references in log files, PM dialogs, CL message boxes or messages sometimes have a different version level. COMPONENT: For the entry package: NVDMEINS.EXE SBODY.EXE NVDMECPY.EXE NVDMEPMS.EXE PMSBODY.EXE For the extended package: NVDMINST.EXE SBODY.EXE NVDMCOPY.EXE NVDMPMS.EXE PMSBODY.EXE NVDMCLT.EXE BODY.EXE NVDMPMC.EXE PMBODY.EXE PROBLEM CONCLUSION: The product version is 2 (NetView DM/2 Ver. 2). PTRNBR: 2M02752 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SEND REJECTED AFTER MANY SEND REQUESTS PROBLEM SUMMARY: In the message.dat an error message is logged 21 times: ANX0852: (E) Too many SEND requests pending. In this situation, sometimes it was not possible sending back a report. If the user wants to send an object via CDM SEND and the message ANX0852 is logged, the desired send does not succeed. INVOLVED MODELES CHANGHED OR ENHANCED ANXSNADS.EXE PROBLEM CONCLUSION: The bad managment of the sends pending was originated by some old send requests not properly managed by the requester so that the status of these requests remains in a not clean condition in the SNA files (ANXSNDIR.SNA). By the fix, the Transmission Controller manages in a better way the requests of sending something coming from the Agent and the user interface attempting to manage also the old pending requests. PTRNBR: 2M02754 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: DEFAULT LOG FILE NOT CREATED ON DOS WORKST. PROBLEM SUMMARY: For the LDU-Receiver installation, the default log file was <bootdrive>:«OS2«INSTALL«ANXINST.LOG, and in case of a Dos WS, as the above directory usually doesn't exist, the log file was not created. COMPONENT: NVDMIREC.EXE PROBLEM CONCLUSION: In case of a Dos WS the default log file is <bd>:«ANXINST.LOG PTRNBR: 2M02755 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: MISSING REBOOT MSG AFTER INSTALLATION PROBLEM SUMMARY: At the end of the LDU-Receiver installation, after the PopUp box desappearing, no message remained on the screen, asking a reboot of the machine, in order to activate the changes done. COMPONENT: NVDMIREC.EXE ANXIIREC.MSG PROBLEM CONCLUSION: A new message ANX8599 was inserted. The message remain after that the PopUp Box desappear. The message is customized for OS/2 and DOS. PTRNBR: 2M02756 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: NVDMINST DOES NOT ACCEPT D: AS TargetDir IN THE RESPONSE FILE PROBLEM SUMMARY: Nvdminst does not accept <driveletter>: as TargetDir in the Response File. It accepts <driveletter>:\ EXECUTABLES MODULES CHANGED OR ENHANCED SBODY.EXE BODY.EXE PROBLEM CONCLUSION Nvdminst changed to accept <driveletter>: as TargetDir in the Response File. PTRNBR: 2M02760 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: LAN SERVER V20 TRAP IF CDM AGENT ACTIVE ON CC CLIENT PROBLEM SUMMARY: A trap occurs when Net Start Server (LS 2.0) is issued on a CC client with CDM agent active COMPONENT: ANXIFCOM.SYS ANXIFCOM.IFS PROBLEM CONCLUSION: An unsupported function was requested calling FS_FSCTL. During this call an invalid parameter was passed to FS_FSCTL so causing a TRAP situation. Now before doing any check on other parameter we look for the requested function: if it is a supported one, ok. Otherwise we return a NO_ERROR Return Code, so avoiding any problem. PTRNBR: 2M02769 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PRESSING HELP ON PENDING REQUESTS PANEL DOES NOTHING PROBLEM SUMMARY: Select 'All Pending Requests...' from the 'CDM - - Catalog' 'Engine' pulldown. When the Pending Request panel is displayed, try to click on the 'Help' button and nothing happens... no help is displayed. There should be some type of help displayed. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: Problem was a missed link between the help in the .HLP file and the Pending Request dialog. To solve that, updated the dialogIdArray adding the dialogId of the Pending Request dialog. This dialogIdArray is then passed to the HelpManager that establishes the link with the .HLP file. PTRNBR: 2M02774 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: IN THE LAN OPTIONS PANEL OF ANXEDINI A KEY IS MISSING PROBLEM SUMMARY: The occurrence appears over an Host LAN attached (Q4) environment. In the Lan Options panel of ANXEDINI utility the MaxRequests key is missing. Moreover there is a confusion when the OK button is pressed because the program exits with a wrong error message that regards the range of MaxRequests Key (NOTE: in the message the key name is unreadable). COMPONENT: ANXEDINI.EXE PROBLEM CONCLUSION: Added the missed spin button 'Max Requests' PTRNBR: 2M02778 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE MESSAGE FOR A WRONG ADAPTER IS NOT CLEAR PROBLEM SUMMARY: If an invalid adapter number is selected, the message that is displayed is wrong. Then, if you press CANCEL and change the adapter, with a correct one, the error is again dispayed. COMPONENT: ANXEDINI.EXE PROBLEM CONCLUSION: The 'Max requests' spin button was missed in this dialog: added it. PTRNBR: 2M02798 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE INSTALLATION TARGET FOR ALL WS IS DELETED PROBLEM SUMMARY: Purge request API deletes the FS and all the CM entries of the GROUP relative to that object. This means that every workstation installation target will be wrongly removed COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: It consists in Purge API deleting only the CM Entry of the GROUP that is the installation target relative to the workstation where the request is to be applied on. PTRNBR: 2M02803 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: A TRAP OCCURS PROBLEM SUMMARY: With this problem it have been tracked three problem: - An Error of CC Server code evaluating the Secondary Effect; - A bad error Log of the DataBase Services; - An Abend Situation in the File Services code. COMPONENT: ANXCMSRV.EXE ANXDBSRV.DLL PROBLEM CONCLUSION: The main problem was in the Agent code because there was an error when decided which were the S.E. (as the Architecture says). Now the code selects the correct S.E. in the Catalog and update them without problem. PTRNBR: 2M02804 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG ERROR MESSAGE FOR AN UNSUCCESSFUL INITIATE REQUEST PROBLEM SUMMARY: Message number ANX0248 has been changed to manage a situation when not only the External install but also the Initiate procedure fails. COMPONENT: ANX.MSG ANXH.MSG PROBLEM CONCLUSION: ANX0248E: (E) The External Install Program specified in Install section or the Initiate procedure '%1' with Global Name '%2' can not be run by the system. System Error '%3'. EXPLANATION: The External Install program or the Initiate procedure cannot be run. It either has a bad EXE/COM format, or is a DOS program which cannot be run in an OS/2 session. The System Error code is the error number returned by the Operating System when it tries to run the specified program: o in the Install section of a Change File o as a local file of a procedure object to be initiated. SYSTEM ACTION: The request ends in error. Other requests are processed. USER RESPONSE: If the request is an initiate, verify the initiate procedure and repeat the request. In case of an External Install determine what caused the error or contact the External Install program supplier. PTRNBR: 2M02808 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: CDM LIST_WS NOT ENOUGH RESOURCES. PROBLEM SUMMARY: The new behavior of the LIST_WS released with CSD XR20276 requires more NetBIOS resources than needed and documented. In fact in the README file of CSD XR20276 a new value of NetBIOS commands, increased by 10, is documented, but increasing this resource by such a value the LIST_WS ends in error. A NetBios trace showed that also 16 sessions and 8 names are needed to correct the problem. COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: The problem has been solved changing the NetBIOS resources requested by the LIST_WS command. Now an increment of 1 session, 1 name and 10 commands is required over those documented in the README file of CSD XR20276. PTRNBR: 2M02809 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG GMT FLAG IN THE UOWC STRUCTURES PROBLEM SUMMARY: In the Agent UoWC structure, the GMT flag (byte 14 of U_of_w_Seqno_DTM) was not encoded in EBCDIC. COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: The fix was made in module ANXECPEC PLS386. PTRNBR: 2M02818 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE PACKAGE COMPRESSED IS NOT COMPLETED PROBLEM SUMMARY: When sending a package compressed with scb algorithm from pc to host and after resend one from host to pc the size is not equal and that is not installable. COMPONENT: ANXLBFS.DLL PROBLEM CONCLUSION: The problem is in the source node, and is in a particular situation, in fact scb compression/decompression is developed on buffer basis and whe input and output buffers terminate simultaneously the fetch module reads from file and overwrites 32k of data to transform.(so 32k of data are lost). The problem has been resolved including a new field in the operation control block to manage this situation. this field is set by anxbfp14 t denote the end of input and output buffers and reset by anxbfp07 after the situation has been managed. PTRNBR: 2M02823 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: UNCOVERABLE ERROR IN PENDING REQUESTS PROBLEM SUMMARY: During a CM request (the commands could be an install or an initiate...) enter in Engine ---> All pending requests ----> Details (press details after that the specified request is selected with the mouse). Because of the request remains in the 'All pending requests' window, if you don't go out, after that the command ends its work press the Push Button 'Details' again. At this point these 2 Pop-Ups appear: 1) Error ANXE5101 The operation failed because of an internal error. Please contact your Product Administrator. rc='0', reason='3315' 2) Error ANXE5449 The request was not found, and could not be displayed COMPONENT: ANXEDTMS.HLP ANXEDTMS.MSG PROBLEM CONCLUSION: Added handle for the following reason codes from '_NdmReceive': 1)CDMERR_PATH_NOTFOUND for CMREQ subdirectory not found 2)CDMERR_CLIPATH_NOTFOUND for the Client subdirectory not found 3)CDMERR_INVALID_REQUEST_ID for an invalid request-id 4)CDMERR_NO_MATCHING_ENTRIES for a not existing request-id Added a new message in the ANXEDTMS.MSG file and the relative Help in the ANXEDTMS.HLP to handle the first two Reason codes: Help for: ANXE5469 The '%1' directory of the product Request/Reply directory cannot be found SYSTEM ACTION: The operation is not executed. USER RESPONSE: Check the subdirectories of the Request/Reply directory to see if the named subdirectory is missing or has been renamed. Retry the operation. The other two Reason codes use an existing message error. PTRNBR: 2M02830 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SYSTEM ABEND 2 CLOSING COMMUNIC.MANAGER WITH PRODUCT ACTIVE PROBLEM SUMMARY: Dos NetBios Thread code didn't handle "NETBIOS environment not defined" return code. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: Added handling of the above mentioned return code. PTRNBR: 2M02848 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: DURING INSTALLATION TO 40 CLIENTS, THE SERVER HANGS PROBLEM SUMMARY: With this PTRNBR new functions have been added into the CC Server to support and manage DOS workstations where a CC Client is installed. COMPONENT: ANXCMSRV.EXE ANXCSCNS.DLL PROBLEM CONCLUSION: Now the CC Server can manage a CC Client on DOS workstation. PTRNBR: 2M02850 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: STARTUP.CMD NOT CORRECTLY UPDATED PROBLEM SUMMARY: Nvdminst does not update the startup.cmd in a migration scenario of the OS/2 1.3 in OS/2 2.0 ( or 2.1 ). Some statements are left. EXECUTABLES MODULES CHANGED OR ENHANCED SBODY.EXE PROBLEM CONCLUSION Startup.cmd is now correctly updated. PTRNBR: 2M02851 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: NVDMINST DOES NOT DELETE IN THE CONFIG.SYS SOME STATEMENTS PROBLEM SUMMARY: Nvdminst does not delete some statements in the CONFIG.SYS in a scenario of migration from rel 1.0 ( or 1.1 ). It happens in particular situations when the customer has installed the rel 1.0 ( or 1.1 ) and has updaded the CONFIG.SYS the rel 1..0 ( or 1.1 ) installation. EXECUTABLES MODULES CHANGED OR ENHANCED SBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION Nvdminst deletes in the CONFIG.SYS all the unhelpfull statements. PTRNBR: 2M02858 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SEND FROM ENGLISH TO JAPANESE SERVER DOESN'T WORK PROBLEM SUMMARY: When a source node with sbcs cp sends a object without description to a machine with dbcs cp, the specific server attempts to translate decription from source to target nod the error. COMPONENT: ANXLBFS.DLL PROBLEM CONCLUSION: The translate operation has been disabled when decription is not present. PTRNBR: 2M02859 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PROC STATEMENT OF NVDM/2 BUILD PROFILE INVALID IN V2 PROBLEM SUMMARY: When executing a Rel1 Package the PROC: statement is not executed. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: Some inconstency between the two formats were corrected. PTRNBR: 2M02864 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: NVDMINST DOES NOT RETURN CORRECT EXIT CODES PROBLEM SUMMARY: Nvdminst does return correct exit code in unattended installation on a Rel 1.0 ( or 1.1 ) EXECUTABLES MODULES CHANGED OR ENHANCED SBODY.EXE NVDMINST:EXE PROBLEM CONCLUSION NVDMINST program changed to retun correct exit codes. PTRNBR: 2M02873 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: UNEXPECTED ERROR LOG PROBLEM SUMMARY: In module ANXEFCQC.C the search handle was not initialized to 0 when the _NdmQuery API was called with ListMode=LIST_FIRST. COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: The handle it's now initialized to 0. PTRNBR: 2M02874 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: UNEXPECTED POP-UP AFTER REQUEST PROCESSED PROBLEM SUMMARY: If a CM request is issued to a NvDM/2 DOS Client powered off, when this client is powered on the request is executed correctly. At the end of the process an unexpected pop-up for a pending request appears even if no actual CM request was queued for the PWS.. COMPONENT: ANXCSCNS.DLL ANXCMLDR.COM ANXCMSRV.EXE PROBLEM CONCLUSION: The problem was due to a missing ACK to the CC server when the ANXCMLDR TSR receives a NetSemClear from the network. To give a solution to this problem the 'NetAwake' command had to be removed from the CC server's code, and a direct query to the DOS Client's queue on the CC server had to be added. PTRNBR: 2M02877 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: A TRAP OCCURS WHEN YOU INSTALL WITH 226 CLIENTS PROBLEM SUMMARY: When more than 226 clients are defined in the WS Table, a trad D occurs in trying to install an object by dialog. COMPONENT: ANXDBSRV.DLL PROBLEM CONCLUSION: The problem has been solved by managing also huge memory segment. PTRNBR: 2M02881 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SPEC LIST WITH /C OPTIONS DOES NOT WORK PROPERLY PROBLEM SUMMARY: The problem is due to Pack/Unpack which does not manage files specified with /C option in the file specification list and they do not exist in the build directory. INVOLVED MODULES CHANGED OR ENHANCED ANXCKPUQ.DLL PROBLEM CONCLUSION: The fix now allows to insert in a change file not existing files which are specified in the specification file list with /C option. Of course the inserted data reguard the file name and the /C option. It has been also changed how the external interface build command options "MUST EXIST" and /C are managed. Now, even if /C specified file does not exist, the "MUST EXIST" option is bypassed. PTRNBR: 2M02886 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PENDING REQUESTS DISPLAY ERROR INF. FOR THE REMOVE PROBLEM SUMMARY: In the Pending Requests Details are displayed error information's when the Remove command is issued. You have an entry installed in IRU Status. Whether you issued the remove in Active area or in Service area always this information's are given you: TargetWorkstation : EMILIA RequestType : REMOVE Status : in progress Global Name : A.A.A.A.REF.1.2 Restore to: Service The error consists of the information regarding the 'Restore to:' In fact if remove command is issued to move the package from the Active area to Service, this field has to be : Restore to: Active. Note: ===== This problem is not present if the CDM LISREQ /WS issued from Command Line because the correct area is always displayed. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: Fixed the problem of Active/Service in the details of pending requests. We were looking at the wrong bytes in the request data structure for the Active/Service value. PTRNBR: 2M02892 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE PM INST IS ENABLE TO DISPLAY THE 8260 MSG PROBLEM SUMMARY: The PM installation of the Server (NVDMPMS / NVDMEPMS) was not able to display the message ANX8260, when needed. COMPONENT: NVDMPMS.EXE NVDMEPMS.EXE PROBLEM CONCLUSION: The described message is now displayed, when needed. PTRNBR: 2M02895 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SEND OF A UPDATED FILE NOT PERMITTED PROBLEM SUMMARY: The send with replace option doesn't work correctly when this operation is invoked from a ndm/2 node to ndm/2 node. in this case the date of the file that must be inserted in the catalog is not correct. Infact are inserted also the first two characters of the year(19) in th catalog. So when the user tries to send the replaced object,the specifi server controls the date of the file with the date in the catalog and gets the error. COMPONENT: ANXBFTH.DLL PROBLEM CONCLUSION: Now the correct date is inserted. PTRNBR: 2M02910 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PERFORMANCE PROBLEM RUNNING PRISTINE INSTALLATION PROBLEM SUMMARY: The problem is due to a not precise use of the threads (the thread for the clock) in a product API. EXECUTABLES MODULES CHANGED OR ENHANCED BODY.EXE SBODY.EXE NVDMCOPY.EXE NVDMECPY.EXE PROBLEM CONCLUSION API changed and the above modules recompiled in accordance PTRNBR: 2M02918 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: FROM REL 1 TO VERSION 2 DOES NOT DELETE OLD DIR PROBLEM SUMMARY: Migrating from NvDM/2 Release 1 to version 2, in an unattended way, changing change target dir (/T:IBMNVDM2), the ANXACTVF does not delete the previous installation directory IBMANX. COMPONENT: BODY.EXE SBODY.EXE PROBLEM CONCLUSION: In case of an unattended installation some empty directories of the previous installatione were not removed. The following directories of the OLDDIR are removed after the IPL IF empty and IF not present in the INI file of the TARGDIR. NVDM/2 V.1 Subdirectories (always) LDU V.2 " (if OLD<>TARGET) CDM V.2 " (if OLD<>TARGET) PTRNBR: 2M02922 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INSUFFICIENT STACK SPACE DECOMPRESSING BIG FILES PROBLEM SUMMARY: Sending big files(10 Mb and above) from a node to another node compressing the file with NVDMLZW algorithm, at the target node sometimes the process terminated because of insufficient stack space. COMPONENT: ANXBFTH.DLL PROBLEM CONCLUSION: The stack in error is the FS thread stack. The size of this thread is increased from 20000 to 25000. PTRNBR: 2M02929 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: PROBLEM OCCURS WITH THE SERVER AND CLIENT NAME PROBLEM SUMMARY: When you used a Client Name include in the Server Name all the request addressed to the Client were processed from the Server. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: There was an error when the product moved the R/R file and when it signaled the Client interested form the request. The problem has been solved changing some check. PTRNBR: 2M02933 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ERROR IN SERVER AFTER MULTIPLE INSTALL ON DOS CLIENTS PROBLEM SUMMARY: At the Host side a plan that performs multiple install,remove, and activate on the some clients was submitted more times. After a lot of time some install were no more executed. COMPONENT: ANXIFSRV.EXE PROBLEM CONCLUSION: The error was originated by the following: when doing a DosFindFirst a DirHandle was allocated by the server to manage following DosFindNext and DosFindClose. Only doing a DosFindClose this DirHandle is deallocated. DOS hasn't a DosFindClose so our redirector calls a Find close ONLY in a particular case. So doing on the server we can have a lot of DirHandle allocated but NEVER deallocated. Doing a stress test, after some time, there were no more DirHandles avaliable so causing the problem we had. The code was modified to have the server to keep track of all DirHandles allocated (and then deallocated) so when a client is stopped we can free all the DirHandles not previously deallocated. PTRNBR: 2M02938 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: DIALOG HANGS IF SOURCE DIR FIELD IS BLANK PROBLEM SUMMARY: If from the CDM - Catalog --> Build from Profile --> Build Change File window, in the "Source directory" field, you specifies the following source directory name: C:« this error message appears: NetView DM/2 Runtime error: "asParameter" not understood. If you leave the "Source directory" field clear, or you specifies the following source directory name: C: the Dialog hangs. COMPONENT: CDMD.EXE VPMSTMGR.DLL VPMBAS14.DLL VPMOFILR.DLL VPMFILE.DLL VPMFLOAT.DLL VPMVM14.DLL PROBLEM CONCLUSION: Now, the source directory has passed as a String instead as a Directory, so the asParameter method is understood. PTRNBR: 2M02949 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: CHANGE CONTROLLER ENDS WHEN THERE ARE ENQUEUED REQUESTS PROBLEM SUMMARY: When the following events are verified at a CC Server WS,Transmission Controller is Active and the Change Controller is Inactive, the Change Controller "ENDS BECAUSE OF ERRORS" when restarted by TC upon an incoming plan received from HOST for a large Group of Client WSs. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: At start time the Change controller tried twice to process the same R/R file. This resulted in a System errror 110 in the Open function. The start up sequence of the Change controller was improoved in order to manage this situation. PTRNBR: 2M02952 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ADD MESSAGES TO CC CLIENT PROBLEM SUMMARY: Lack of CC Client messages when managing events such as: - no TSR (ANXCMLDR.COM) loaded for DOS CC Client workstation - DOS CC Client does not support Reldata resource - INITIATE can not run a program on OS/2 or DOS platform COMPONENT: ANX.MSG ANXH.MSG PROBLEM CONCLUSION: Added three new CC Client messages which ANX1326, ANX1327 and ANX1329 to manage events such described in PROBLEM DESCRIPTION section. PTRNBR: 2M02958 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: MANY UNRECOVERABLE ERROR ON CLIENTS PROBLEM SUMMARY: A wrong error log was done in an error condition by the CC Server COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: Now the correct component name is stored into the error log file. PTRNBR: 2M02960 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: A TRAP OCCURS WHEN YOU ARE MANY INSTALL REQUESTS PROBLEM SUMMARY: With about two thousands Request enqueued to the Change Controller but still not yet processed (i.e. not yet enqueued to the Clients ) a TRAP occurred COMPONENT: ANXBASE.DLL ANXDBSRV.DLL ANXCMSRV.EXE PROBLEM CONCLUSION: There was a System overhead for too many Segment allocated. Moreover Some deallocation of Shared Segment were missing, this filled up the System Handle for Shared Segment. The Memory Segment Allocation was optimized and all the pending Gets of Shared Memory were checked and free. PTRNBR: 2M02966 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE PM INST IS ENABLE TO DISPLAY THE 8260 MSG PROBLEM SUMMARY: The PM installation of the Client (NVDMPMC) was not able to display the message ANX8260. COMPONENT: NVDMPMC.EXE PROBLEM CONCLUSION: Now the described message is correctly displayed, when needed. PTRNBR: 2M02985 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SAME MNEMONICS IN THE "CC DOMAIN" ACTION BAR PROBLEM SUMMARY: In the "CC Domain" window, the action bar has the same mnemeonics for "Workstations" and "Windows" COMPONENT: CDMD.EXE PROBLEM CONCLUSION: The following changes have been done: 1) The Workstation pull down in the CC Domain window have the mnemonic character = 'k' 2) The CC Domain item in the Windows pull down in the Remote Destinations window and in the Message Log window had before as mnemonic character 'C', but this was the mnemonic character of the Catalog item too. So I change the mnemonic character of CC Domain item in 'D'. Naturally, this change has been done in all the CDM windows - Windows pull-down. PTRNBR: 2M02992 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: MSG ANX0076 (E) SHOULD BE CHANGED IN (W) PROBLEM SUMMARY: The following message: ANX0076: (E) The SNA/FS Server ended, as requested by the Transmission Controller issued by the Specific Server after an Activate Request should be written as a warning or, better, informational message. COMPONENT: ANX.MSG PROBLEM CONCLUSION: The message: ANX0076: (E) The SNA/FS Server ended, as requested by the Transmission Controller is changed in: ANX0076: (I) The SNA/FS Server ended, as requested by the Transmission Controller Also the Documentation is changed: ANX0076 (I) instead of ANX0076 (E). PTRNBR: 2M02994 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: RUNTIME ERRORS WHEN PRESS MORE TIME DETAILS BUTTON PROBLEM SUMMARY: If enter in All Pending Requests, then you selected a request with the mouse and press more times the DETAILS Push Button this error Pop-Up appears: Runtime error:"asString"not understood. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: The problem has been fixed by making sure that the details button cannot be pressed while we are working on the first request. PTRNBR: 2M02996 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: WRONG HELP FOR THE ANXE5469 PROBLEM SUMMARY: Wrong help for the ANXE5469 Pop-Up. This Pop-Up says: ANXE5469 The Request Details failed because the subdirectory 'XXXXXXX' of the Request/Reply directory cannot be found If press HELP in this Pop-Up this no much message is displayed: 'The '%1' directory of the product Request/Reply directory cannot be found' What is '%1' meaning ? Surely, it is the directory name but in this way is not comprehensible. COMPONENT: ANXEDTMS.HLP PROBLEM CONCLUSION: The following two help have been changed: The '%1' has been replaced with the string 'named', in both the help messages. Help for: ANXE5469 The named directory of the product Request/Reply directory cannot be f SYSTEN ACTION: The operation is not executed. USER RESPONSE: Check the subdirectories of the Request/Reply directory to see i Help for: ANXE5470 The Delete for the Workstation failed because the relative subdirecto r USER RESPONSE: Ensure the named subdirectory of the Request/Reply directory is ... SYSTEN ACTION: The operation is not executed. PTRNBR: 2M02997 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: NO DEFINED HELP IN SOME POP-UP PROBLEM SUMMARY: In some Information Pop-Up no Help is defined. COMPONENT: ANXEDTMS.HLP PROBLEM CONCLUSION: Online HELP added to the following messages: ANXI5707,ANXI5708,ANXI5197,ANXI5196,ANXE5263,ANXE5467,ANXE5664, ANXI5195,ANXI5194,ANXI5198,ANXI5193,ANXI5199,ANXI5711,ANXI5709, ANXI5710 PTRNBR: 2M02998 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: HELP NO COMPREHENSIBLE FOR THE ANXI5703 PROBLEM SUMMARY: During starting Dialogs, if the Transmission Controller is down this Information Pop-Up is displayed: ANXI5703 The Transmission Controller is in the process of being started If press the Help Push Button this explanation is given: The operation cannot complete because Transmission Controller is busy completing a previous command Why is there this help for this message? I think that there is no logical connection between this two explanations. The above error occurs also in the ANXI5704 Pop-Up. This message is displayed during a Shutdown command. The explanation message: The operation cannot complete because Transmission Controller is busy completing a previous command also in this case is not right because in this case no process was using the Transmission Controller completing a previous command COMPONENT: ANXEDTMS.HLP PROBLEM CONCLUSION: The HELP text is changed as follows: Help for: ANXI5704 The Transmission Controller Manager is in the process of being Quiesced. You can check its status later to see if it is inactive. USER RESPONSE: Wait for the Transmission Controller to complete Quiescing. Help for: ANXI5703 The Transmission Controller Manager is in the process of being Starte d You can check its status later to see if it is active. USER RESPONSE: Wait for the Transmission Controller to start PTRNBR: 2M02999 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: TRAP IF IN ACTIVATE POP-UP THERE IS NO WORKSTATION PROBLEM SUMMARY: From the Main Menu press Windows then CC Domain. Before that this window is displayed with all workstations, I can press Selected then the Activate command. At this point the Activate window is open, but in he the Workstation field no workstation is displayed (the field is empty). If press the Push Button 'Activate' a CDM --CC DOMAIN TRAP 000D is displayed. The module that goes in Trap is the ANXEFAPI.DLL. After that the Dialogs is closed. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: The Activate dialog didn't disable the 'Activate' push button when the CLients list box was empty. I fixed this problem in this dialog, and in the Delete Workstation dialog too. More, in order to avoid to have the Selected pull down enabled when the window is opening and the clients are no in the list yet (this happens specially in the slow machines), we disable the the menu before the clients are listed. Since we could have the same behaviour for the other windows we did this disable operation for the Selected menu of all the CDM windows. PTRNBR: 2M03006 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: DIALOGS PREVENTS ALL MACHINE PROCESSES TO WORK PROBLEM SUMMARY: The machine hangs and no process works anymore, in a particular situation such below described. All CDM tasks are down (the Change Controller, the Transmission Controller and the Agent). Start the Dialogs with the CDMD command. During the starting the ANXI5195 and the ANXI5703 Pop-Ups are displayed. Press the 'Help' Push Button on the first Pop-Up and leave running this Pop-Up and its Help; wait for that the second Pop-Up appears and then press also here the 'Help' Push-Button. At this point all tasks hang and the only solution is to power off the Workstation. COMPONENT: CDMD.EXE PROBLEM CONCLUSION: This problem has been fixed. The cause was the design of our "modeless" message box, which has been slightly changed now. There will be no external changes except that the hang should not happen anymore. PTRNBR: 2M03007 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INCORRECT REPORT TO THE HOST PROBLEM SUMMARY: A bad report was sent to the Host because the Workstation Name was not padded to '40'X. The problem occured because we passed it to the Message Routine specifing a bad Var Type and the Message Routine changed the variable in a ASCII Z terninating string. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: The problem has been solved passig the correct Var Type in each modules that write the message the the request has been purged. PTRNBR: 2M03018 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: OS/2 TRAP WHEN PERFORMING SNA OPERATION ON APPC CONNECTED WS PROBLEM SUMMARY: The problem is that when the Agent is started and a request arrives for it,the ANXIFRV.DLL goes in trap because the Agent when it is already started tries to kill the other Agent started from the TC passing to the ANXIFSRV.Dll bad pointer. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: The exit routine of the Agent will work only when all the areas and pointers are acquired. PTRNBR: 2M03021 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ANXSNDIR.SNA IS NOT MIGRATED FROM V1 TO V2. PROBLEM SUMMARY: Due to a partial migration from a NVDM/2 V.1 to NVDM/2 V.2 Q4 environment (after an intermediate migration to a Q3 Env) the CM request incoming from the Host towards the CLIENTs of the Q4 machine were not processed. COMPONENT: SBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION: Now, running the described scenario, the CM request incoming from the host to the CLIENT of the migrated server are correctly processed. PTRNBR: 2M03022 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INSTALLATION EXECUTABLES DOESN'T INTERACT CORRECTLY WHIT THE USER PROBLEM SUMMARY: When displaying the pop-up, command line installation executables (NVDMINST.EXE, NVDMCLT.EXE, NVDMCOPY.EXE, NVDMEINS.EXE, NVDMECPY.EXE) don't clear the screen; but, when the installation completes with an error or is stopped with a CTRL-C, the screen contents are not restored. Moreover, if the user is installing the product from a removeabel media, the screen portion underlying the diskette request pop-up is not restored. COMPONENT: For the entry package: NVDMEINS.EXE SBODY.EXE NVDMECPY.EXE For the extended package: NVDMINST.EXE SBODY.EXE NVDMCLT.EXE BODY.EXE NVDMCOPY.EXE PROBLEM CONCLUSION: The screen is cleared before drawing the installation pop-up. If a CTRL-C or CTRL-BREAK is issued before the installation pop-up has been drawn, the user receives the system response. If a CTRL-C or CTRL-BREAK is issued after the installation pop-up has been drawn, the screen is cleared and the installation interruption message is displayed on the screen and logged on the installation log file(s): The process has been interrupted by the user If the installation is interrupted using the CTRL-C or CTRL-BREAK, clean-up operations will be performed (remove temporary directory, restore configuration files, and so on) before return control to the user. These operation will be executed also if the session where the installation is running is closed from the task list. PTRNBR: 2M03023 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INTERNAL ERROR IN MODULE ANXEFCBL.C PROBLEM SUMMARY: On some workstation, there is a random problem while building a change file; the commands prompts for a new diskette even if the source directory is not a diskette drive. moreover, a C language run-time message is generated. COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: The random problem is not eliminated but you do not have that C run-time message anymore. PTRNBR: 2M03034 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ACTIVATE ON CLIENT DOES NOT MOVE EAS OF EMPTY DIR. PROBLEM SUMMARY: Directory EAs are not moved from service area to active area during an ACTIVATE function COMPONENT: ANXCMCLC.EXE at Client WS ANXCMCLS.EXE at Server WS PROBLEM CONCLUSION: The Directories EAs management has been reviewd in the code of the ACTIVATE function PTRNBR: 2M03041 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: MIGRATING FROM Q4 TO CLIENT MORE OLD DIRS AREN'T REMOVED PROBLEM SUMMARY: During a migration form a Q4 Environment (i.e. Host-Connected Server machine) to a Client Environment, with the product inactive, some unused empty directories were not deleted. COMPONENT: BODY.EXE PMBODY.EXE PROBLEM CONCLUSION: Now, in such a migration, with the product inactive, the unused empty directories are no more kept. PTRNBR: 2M03048 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: ERROR IF MAXCLIENT IN INI FILE IS GREATER THAN 96 PROBLEM SUMMARY: If in the IBMNVDM2.INI file we specifies a number of Clients greater than 96 the CMLOADER doesn't start because no sufficient resources are available. COMPONENT: ANXIFSRV.EXE ANXIFSRV.DLL PROBLEM CONCLUSION: To solve another problem two new field were introduced in a structure used to save all data regarding all clients connected to the server (one for each client). All these data are saved in a shared segment and, before starting the server a check is done to see if we have enough memory to save all them. Adding this two new fields we exceeded the memory available if client number (MAXCLIENT in IBMNVDM2.INI) is greatest than 96. Now we reduced the size of another field (this is not very influent).. However we plan to implement a new and more elegant solution in the next CSD. PTRNBR: 2M03050 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE CDM START COMMAD AFTER THE SHUTDOWN CAUSES A CC ERROR PROBLEM SUMMARY: The problem is that when the user made consequently Cmd start and Cdm shutdown on a Ps/2 very fast (95) the Change Controller ends because of errors. COMPONENT: ANXCMSRV.EXE PROBLEM CONCLUSION: The solution is to elinate the pop-up message when the Agent encounters a particular return code from the Tc. PTRNBR: 2M03057 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: SUCCESS VIO POPUPS APPEAR PROBLEM SUMMARY: With the 'CDM CANCEL' command the blue VIO popups successfully appear. This is extremely annoying because in a Presentation Mgr environment, the vio pop-ups interrupt a users work flow by popping up and requiring him to press ENTER. COMPONENT: ANXCMSRV.EXE ANXCMCLT.EXE ANXPULAG.DLL PROBLEM CONCLUSION: The problem is due to set missing, and the message was in a POPUP. Now is set a variable to do a message without POP UP. PTRNBR: 2M03076 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: BUILD FROM HARD DISK REQUIRES DISKETTES PROBLEM SUMMARY: The problem occurs to customer as well as in this lab (PMR 9x274) Building from hard-disk, NetView DM/2 prompts you to insert another diskette even if you build from hard-disk source directory Besides, even if you insert the diskette, the BUILD fails. After examining the problem, it has been found out that: The PACK/CHECK PACK service, while checking for drive type open the drive with OPEN_ACCESS_READWRITE + OPEN_SHARE_DENYREADWRITE: this causes return code 32 on some workstations. COMPONENT: ANXCKPUQ.DLL PROBLEM CONCLUSION: It has been tested that OPEN_ACCESS_READONLY + OPEN_SHARE_DENYNONE is enough for the pack purpouses and does not cause that problem anymore on those workstations as well as other workstations. PTRNBR: 2M03097 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: IT'S IMPOSSIBLE TO EXECUTE A /CO FROM BIN WITH THE ENTRY P. PROBLEM SUMMARY: Scenario: Host attached WS (Q3) environment created from the Entry Package images created by NVDMECPY. After a successfully installation I have tried to re-configure the product issuing a /co command from the BIN subdirectory. This command fails with the message "Enable to start the second step of the installation". The problem arises because in the BIN subdirectory there aren't the following necessary files: ANXIIM12.EXE and ANXIIM12.DLL. COMPONENT: ANXF.LST (these are not executable modules but list processed ANX1.LST by installation programs) PROBLEM CONCLUSION: In the first list file ANX1.LST of the Entry package, the two files needed for the product configuration (ANXIIM12.*) were not uploaded to the target directory. The list files were modified. PTRNBR: 2M03102 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INSTALLATION OF NVDM/2 DOESN'T WORK CORRECTLY PROBLEM SUMMARY: Is not possible to stop the installation with Ctrl+C command when the installation pop_up is asking for the next diskette. COMPONENT: BOSY.EXE SBOBY.EXE NVDMCOPY.EXE NVDMECPY.EXE PROBLEM CONCLUSION: Now, the user can stop the installation even during the diskette requesting. PTRNBR: 2M03130 APARNBR: PJ08653 PTFNBR: XR20302 EXTERNAL SYMPTOM: INSTALL ON NETWARE SERVER SCENARIO NOT SUPPORTED PROBLEM SUMMARY: The Scenario "Distribution to a NetWare Server" reported in the Appendix B of the NetViw DM/2 Installation and Customization Guide is not completely supported. If the remote Drive with which the NvDM/2 Server see the NetWare Server is not defined as a Shared Area, the installation is rejected. Drive that is differ This is due to the limitation of installing on remote drive different from SA: or SB: The scenario already supported in the rel 1 and commited in the RFA must be supported. COMPONENT: ANXCMCLC.EXE ANXCMCLP.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: There is a check that allows only the Server WS to install on remote drives only if they are a Shared Areas The check is removed: The Server WS can address remote Target Directory only if the AlterActiveComponent=YES PTRNBR: 2M03000 APARNBR: PJ08657 PTFNBR: XR20302 EXTERNAL SYMPTOM: THE C: TARGET DIR NOT ALLOWED IN TARGET DIR PROBLEM SUMMARY: Target dir in a change file does not accept C: . COMPONENT: ANXEFAPI.DLL PROBLEM CONCLUSION: The code has been changed to accept either drive or path, i.e. C: or C:« . PTRNBR: 1000072 APARNBR: PJ08760 PTFNBR: XR20302 EXTERNAL SYMPTOM: DISTRIBUTOR HANGS WHEN THE RECEIVER GOES DOWN PROBLEM SUMMARY: If a receiver goes down in a sudden way because of a OS/2 Seesion Endcaused by the user or by an external trap while it is connected to the distributor,the distributor itself hangs waiting for an answer never coming. No action is taken to follow the distribution to the other receiver or to finish the distribution in order to start again listening other receiver waking up. COMPONENT: LDS.EXE LDSDMSG.MSG PROBLEM CONCLUSION: A timeout related to the maximum time interval that a distributor has towait for a receiver answer is introduced. This has been introduced by an environment variable LDSXOUT that if set to a number in the range 1-9999 should be the maximum amount of time that the distributor waits for the completion of any trasmission command (send or receive) In case this timeout is reached the receiver name is marked as red in the distributor panel, the netbios session is closed and a message is logged in the distributor log file saying the timeout is reached and the receiver has been disconnected. More the NCB control block is logged too, to show the cause of disconnection. PTRNBR: 1000074 APARNBR: PJ08760 PTFNBR: XR20302 EXTERNAL SYMPTOM: COMPATIBILITY WITH OTHER DOS APPLICATIONS PROBLEM SUMMARY: The DOS LDU receiver works resetting the adapter. This cause the adapter to cancel any netbios table and cause the destruction of other application netbios resources. The better solution should be to reset the adpater only in case the User asks for this action. COMPONENT: LDSR.EXE LDSRMSG.MSG PROBLEM CONCLUSION: A new environment variable has been added LDSRESETD. If this variable is set to ON the flow of the program is the same as before: a reset of the adapter has made even in the Dos environment and thus any previous record in the netbios tables is deleted. Setting the variable to any other value or not setting it cause that in DOS mode the code now does not reset anymore the adapter and in this sense the user doesn't know the availabilityof the NetBIOS resources unitl the code use it. In DOS MODE at the end of the distribution the receiver frees the session and delete its name in order to make them available again instead od resetting the adapter again. APAR PJ06353 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- PURGE REQ DOES NOT UPDATE THE CHECKPOINT FILE COMPONENT: ANXEFAPI.DLL ANXCMCLS.EXE --------- PROBLEM SUMMARY: ---------------- If the CM request is purged, the checkpoint file (ibmnvdm2.cck) is not updated according with the purge command. APAR PJ07066 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- NVDM2 MAINT. SYSTEM INSTALL FAILURE WITH MSG ANX8223 COMPONENT: BODY.EXE SBODY.EXE PMBODY.EXE PMSBODY.EXE ANXIIDDB.DLL --------- PROBLEM SUMMARY: ---------------- Customer is attempting to install a NVDM/2 maintenance system on the D: drive of a client and is failing with Message ANX8223 An unexpected OS/2 error SYS0003 occurred copying file ANXACTVF.@XE APAR: PJ07089 PTF: XR20273 ========================== EXTERNAL SYMPTOM: ----------------- CDM MISCELLANEOUS FIXES COMPONENT: ---------- THIS APAR REFRESHES GA CODE PROBLEM SUMMARY: ---------------- This is a miscelaneous APAR to fix all the CDM fixes that are cumulated from CSD XR20273 but they don't have their own APAR. The list of the fixed bugs is the following: 1 - ACTIVATE: PROBLEMS CREATING DIRECTORIES WITH LONG NAMES 2 - INITIATE: RC=0 IS SENT TO HOST ALSO IF THE PROCEDURE FAILS WITH RC=8 3 - MULTIPLE INITIATE FAILS WITH 085A000 AND 085C001 SENSE CODE 4 - UPGRADE SERVER: THE IPL POP-UP DOES NOT DISAPPEAR 5 - WRONG SENSE CODE FOR ACTIVATE WITH FORCE=NO 6 - OPTICAL DISK 7 - MOVING DATA BASE ACCESS IN AGENT COMPONENT 8 - MESSAGE LOOP FROM A SENDER TO A RECEIVER 9 - INCORRECT BEHAVIOUR IF RESOURCE IS NOT UNIFORM TEXT 10 - ERROR LOGGING LOCALLY USING NVDMBDSK 11 - LOGGING OF EXTINST INVOK.PARMS IN DM2 LOGS 12 - NVDMCOPY FOR 5.25 BUILD WORKS WRONGLY 13 - TWO EASY WAY TO KILL CDM AGENT 14 - MULTIPLE INITIATE REQ.FOR AN OBJECT IN THE SAME WRK 15 - WRONG INITIATE RETURN CODE TO THE HOST 16 - INC.PROCESS OF NVDM2 FOLDER & ICON DUR.MIGRATION 17 - IT IS NO POSSIBLE REMOVE THE INST.PANEL ON SCREEN 18 - NVDMPMS: TIMEZONE IS NOT MANAGED CORRECTLY 19 - MSG TO INSERT DISK IN PM INSTALLATION IS WRONG 21 - "SA:" & "SB:" NOT SUPPORTED IN FILESPECLIST 22 - REPORT NOT SENT AFTER ACTIVATE 23 - SYNCHRONIZATION PROBLEM 24 - MESSAGE LOOP FROM SENDER NODE AND THE RECEIVER 25 - DOCUMENT.: WHAT TO DO WHEN CM REQ. ABORTS FOR T.C NOT CONFIG. 26 - DOCUMENTATION:WRONG SCENARIO IN THE USER GUID 27 - ACTIVATE:THE EMPTY DIRECTORIES AREN'T CREATED 28 - CC CLIENT FAILS WHEN CC SERVER STARTED: ANX0209 29 - NVDMINST:WRONG END OF THE PRG. GIVING AN INVALID SOURCE DIR 30 - IF THE DISTRIB. IS IN THE INTERM. NODE NO REPORT HAS TO BE SENT. 31 - HAS TO BE DOCUMENTED A SCENARIO TO INSTALL MORE TIMES THE SAME CHANGE FILE 32 - DIALOG: THE FIELD IS NOT EMPTY 33 - DIALOG: PROBLEMS OCCUR IN Q3 ENV. IF IT WAS MIGRATING FROM REL1 34 - DOC: SEVERAL PROBLEMS ON THE MANUALS 35 - DOC: THE MESSAGE ANX8412 "MIGRATION NOT ALLOWED" IS WRONG 36 - INSTALL.: ADD IN THE INSTALL. PANELS THE DISKETTE 37 - DIALOG:NO TASK IS LOGGED IN TASK LIST DURING 38 - DOC: A WAY TO SUPPORT ANY CHARACTER IN THE SPECIFICATION 39 - DIALOG:THE DIALOGS HANG WHEN PRESS TWICE THE TRACE COMMAND 40 - THE EIGHTH DISKETTE IS NOT REQUESTED DURING THE INST.OF ENTRY 41 - DOC:PARAGRAPH "PARTIALLY UNATTENDED MODE" MU 42 - ANXEDINI:A WRONG VALUE FOR TRANSFORM PARAM. I 43 - WRONG FUNCTION BEHAVIOUR DESCRIPTED IN THE U.G. 44 - MORE ROBUST ERROR MESSAGE NEEDED FOR EXE WITH DLL'S 45 - FROM R1. REPORT NOT SENT TO HOST 46 - THE CHECK IS MISSING IF I DEFINE ADAPTERNUM=1 47 - PROBLEMS WHEN TRYING TO INSTALL AN OBJECT INTO SHARED AREA 48 - ANX0248 -- ERROR ON INVOKING INSTALL PROGRAM 49 - UPGRADING A CLIENT TO A SERVER 50 - /CO OPTION WITH /S SHOULD NOT CAUSE INSTALL TO FAIL 51 - CID -- PRISTINE CLIENT NEEDS RETURN CODE WHEN REJECT INSTALL 52 - CID: PRISTINE INSTALL SEQUENCE INCORRECT OR LOST 53 - README NEEDS TO DOCUMENT PROBLEMS WITH LS SERVER 3.0 54 - MESSAGES MISSING IN MESSAGE AND ERROR RECOVERY GUIDE 55 - INCLUDE SUBDIRECTORIES OPTION DOES NOT WORK 56 - CID: ASSISTANCE WITH LS 3.0 SERVER PROBLEM 57 - TRAP C OCCURS IF NVDMUFM IS ISSUED AND COMM MGR IS DOWN 58 - NVDM2 INSTALL FAILS IF USING ALTERNATE TOKEN ADAPTER 59 - DOC:IMPLEMENTATION OF PMR REFERRING TO COMM MGR CONFIG.UPDATING 60 - NVDMINST : THE SEQUENCE OF THE DISKETTES IS WRONG 61 - DIALOG DOESN'T WORK AFTER SOME OPERATIONS 62 - CID: IMPOSSIBLE TO INSTALL NVDM2 CSD WITH EXT INSTALL 63 - CID: PRISTINE MACHINE SCENARIO ON A MACHINE WITHOUT PARTITION 64 - A MESSAGE IS MISSING IN NVDMCOPY 65 - ANXE5189 IS INFORMATIONAL NOT ERROR 66 - CC DOMAIN DIALOG SHOULD BE REFRESCHED 67 - CID: PRISTINE SCENARIO INCORRECT SEQUENCE 68 - ERROR IN PROFILE IS NOT PICKED UP UNTIL INSTALL 69 - NEED TO DOCUMENT FS: DOCUMENT PARAMETER FOR CDM BUILD 70 - CSD INSTALLATION PROCEDURE HAS TO BE DOCUMENTED 71 - INITIATE DOES NOT SUPPORT MORE THAN ONE PARAMETER. 72 - A PROBLEM OCCURS DELETING FILES AT THE INSTALLATION TIME 73 - DELETE WS DOES NOT ALLOW TO OPEN OTHER PANELS. APAR PJ08405 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- GLOBAL NAME NOT DISPLAYED IN ANX0090 AND ANX0099 COMPONENT: ANXCMSRV.EXE --------- PROBLEM SUMMARY: ---------------- When the message ANX0090 is issued: The characters %1 are displayed instead of the Global Name name. The same problem occurs with the message ANX0099: APAR PJ07570 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- CC SERVER GO DOWN WHILE DELETE A R/R FILE. COMPONENT: ANXCMSRV.EXE --------- PROBLEM SUMMARY: ---------------- During the normal processing of the too many request if the Customer issue the ListReq command can occur that the CC Server go down becasue it is not able to delete the R/R File in use from the ListReq command. APAR PJ07580 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- ANX8411 PATH STATEMENT TOO LONG DURING NVDM2 V2 INSTALLATION COMPONENT: BODY.EXE,SBODY.EXE,PMBODY.EXE and PMSBODY.EXE --------- PROBLEM SUMMARY: ---------------- REMOVED 256 CHARACTER LENGTH LIMITATION FOR PATH STATEMENT INTO COBFIG.SYS APAR PJ07759 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- CDM-CATALOG ENTRY NOT DELETED FROM THE WINDOW LIST COMPONENT: CDMD.EXE --------- PROBLEM SUMMARY: ---------------- After the CDM-CATALOG window is presented, click on the system menu to Close the window and the application, in spite of this the CDM catalog entry on the windows list is still present. APAR PJ07798 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- LDU MANAGER DOSN'T RECOGNIZE THE REMOTE SYSTEM DRIVES WHEN USING NOVELL COMPONENT: LDSMGR.EXE --------- PROBLEM SUMMARY: ---------------- If a NOVELL redirected drive is selected in the directory tree window, a MSG008: drive diskette not ready is returned because of a bad management of a return code coming from a OS/2 system call. The return code is not correctly managed and the drive is accessed even thougth the queue has status released. APAR PJ07811 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- SOURCE DIRS NAMED IN MIXED CASE NOT REMAPPED BY LDU COMPONENT: LDS.EXE --------- PROBLEM SUMMARY: ---------------- When distributing files where the source subdirectory name is in mixed CASE, the remapping of the subdirectory at the target system does not take place for the create directory function. the remapping for the file transfer works properly. LDU fails at the target system if the source drive letter is greater than the highest drive letter on the target system. APAR PJ07812 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- DEVICES C: AND D: CHECKED EVEN IF THE VARIABLE SPACECHECK ISN'T SET COMPONENT: LDSR.EXE --------- PROBLEM SUMMARY: ---------------- The devices should be checked only in case SPACECHECK environment variable is set to on to prevent customer intervention when the distribution is actually running. This was carried out even the aforementioned variable was set to off causing user intervention when the D drive is removable with the diskette not inside. APAR PJ07852 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- DURING INSTALLATION TO 40 CLIENTS, THE SERVER HANGS COMPONENT: ANXCSCNS.EXE --------- PROBLEM SUMMARY: ---------------- The OS/2 scheduler didn't schedule the NetBios thread and the PWS was hanging. APAR PJ07878 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- WRONG DRIVE LETTER IN MESSAGE ANX0148W COMPONENT: ANX.MSG --------- PROBLEM SUMMARY: ---------------- The message ANX0148 is changed in: There is a removable diskette inserted. Also the user response has been changed. APAR PJ08055 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- INSTALL FAILS IF ACCESS MODE SPECIFIED FOR SHARED DIRS COMPONENT: SBODY.EXE PMBODY.EXE PMSBODY.EXE --------- PROBLEM SUMMARY: ---------------- Product installation fails if access mode is specified, according to the manual SH19-6915-00 (Installation and Customization Guide Version 2) at page 112,for any Server shared directory. APAR PJ08178 PTF: XR20276 ========================= EXTERNAL SYMPTOM: --------------- CDM MISCELLANEOUS FIXES COMPONENT: --------- ANX.MSG ANXCAPMC.EXE ANXCKPUQ.DLL ANXCMCLC.EXE ANXCMCLP.EXE ANXCMCLS.EXE ANXCMSRV.EXE ANXCSCLI.DLL ANXCSCNN.DLL ANXCSCNP.DLL ANXCSCNS.DLL ANXCSSRV.DLL ANXDBCLI.DLL ANXDBSRV.DLL ANXDLG.DLL ANXEFAPI.DLL ANXH.MSG ANXIFCOM.DLL ANXIFCOM.IFS ANXIFCOM.SYS ANXIFPID.SYS ANXIFPID.SYS ANXIFREQ.DLL ANXIFREQ.DLL ANXIFSRV.DLL ANXIFSRV.DLL ANXIIDDB.DLL ANXIISNA.EXE ANXLBFS.DLL ANXLCMS.DLL ANXLCPB.DLL ANXPULAG.EXE ANXSNADS.EXE CDMD.EXE CDMSPV.EXE DCC.EXE LDSR.EXE LDSMGR.EXE NVDMBDSK.EXE NVDMPMS.EXE NVDMPM.EXE NVDMCLT.EXE NVDMCOPY.DLL NVDMDSK.EXE NVDMECPY.EXE NVDMEINS.EXE NVDMEPMS.EXE NVDMINST.EXE NVDMLZW.EXE NVDMPCSD.EXE NVDMPMC.EXE NVDMPMS.EXE NVDMRCSD.EXE NVDMUFM.EXE PMBODY.EXE PMSBODY.EXE SBODY.EXE PROBLEM SUMMARY: --------------- Miscellaneous APAR opened to address all the fixes not related to existing APARs. 1 - INSTALL:THE EMPTY DIRECTORIES AREN'T CREATED (TRL - INRU) 2 - DOS INST: INCONSISTENT MESSAGES FORMAT 3 - NVDM/2 BOOTABLE DISKETT MUST BE LEFT IN THE BOOT DRIVE 4 - DOS CM_INIT.:(FREE) FAILS ON OS/2 CLIENT IF PROC IS A ".COM" 5 - MIGRATION Q4+LDU -> Q2IL : SOME PROBLEMS RUNNING ON GA CODE 6 - NVDMLZW : THE HELP FLOW ISN'T DISPLAYED IN OS/2 WINDOW 7 - CDM AGENT ENDS CONTINUOSLY IN UNRECOVERABLE ERROR 8 - CSD: UTILITY NVDMENV NOT AVAILABLE WITH DCR 108 9 - TRAP OCCURS INSTALLING AN OBJECT IN TRIAL ON A CLIENT 10- CID:WRONG CLIENT RE_INSTALLATION ON FAT SYSTEM 11- TRAP ERROR TRYING TO SEND RESOURCES FORM NDM 1.4 VS NDM/2 12- THE COMMAND LINE INSTALLATION DOESN'T WORK 13- DOS INST: WRONG ERROR MESSAGES 14- MSG ANX0248 AND ANX0237 HAVE TO SHOW AUXILIARY CODE 15- AT CDM START MSG ANX01015 ISSUED AND STARTS FAILS 16- DELETE WS /F DOESN'T LET THE AGENT COMPLETE THE PENDING REQUEST 17- INCORRECT PROCESSING OF CDM ICON UNDER OS/2 1.3 18- SHARED DIRECTORIES DETACHED BEFORE CLOSING CHECKPOINT FILE 19- WRONG NETWORKSEMAPHORE ERRORLOG 20- CLOSING THE CDM DIALOG BEFORE ENTRIES ARE PRESENT HANGS SYS 21- (FREE)DOS CONVERS: CDM LIST_WS DOES NOT WORK PROPERLY 22- DIRECTORY EA'S NOT INSTALLED IF THE DIRECTORY IS EMPTY 23- OS2 INSTALL:UNPACK OF A SPECIFIC COMPRESS.FILE DOES NOT WORK 24- CDM AGENT FAILS AFTER AN ACTIVATE 25- HOST LOOP DUE TO A NVDM2 ERROR 26- 801C0001 IS DETECTED AFTER A LINE FAILURE 27- MESSAGE ANX8411 NOT DOCUMENTED 28- MORE FILES ARE NOT MOVED INSTALL. THE CLIENT WITH THE PM PR 29- NVDM/2 BOOTABLE DISKETT MUST BE LEFT IN THE BOOT DRIVE 30- CDM START CANNOT OPEN THE CATALOG. 31- DON'T ATTACH SHARED DIRS AFTER LINK FAILURE 32- CDM AGENT AND CDM MANAGER GO DOWN FOR NB PROBLEMS 33- CLIENT AGENT GO DOWN IF IT LOOSES THE LINK WITH THE SERVER 34- CID:ANY WS GO DOWN AFTER ABOUT A THOUSAND OF INSTALLATION 35- START:NO MSG IS DISPLAYED WHEN ENTER WRONG PARM ON A CLIENT 36- NVDM 1.4: LOOP DURING A RESTART MECHANISM 37- DOS REMOVE(FREE): REMOVE FAILS AFTER A DELETEWS COMMAND 38- UNCATALOG FAILS FOR A TEN TOKENS OBJECT 39- REWORD CLIENT MESSAGE 40- (FREE) WRONG WORD IN WARNING MESSAGE 41- DOS EX_INST.: IT DOES NOT WORK IF EXT PROG. IS A '.BAT 42- CM-ACTIVATE: INCORRECT MESSAGE IN DRIVE CHECKING 43- THE SERVER INSTALLATION (VIA DISKETTES) DOESN'T WORK 44- IT'S IMPOSSIBLE TO INSTALL THE LDU WITH THE PM ENTRY PROGRAM 45- NVDMINST:THE MESSAGE ANX0266W IS WRONG 46- PROBLEMS OCCUR USING AN INVALID SOURCE DIR (WITH PM INST.) 47- NVDMPMC : AN UNEXPECTED MESSAGE IS ISSUED DURING MIGRATION 48- WRONG UPDATING OF STARTUP.CMD DURING MIGRATION 49- PROBLEMS WITH THE CLIENT MIGRATION CHANGING TARGETDIR 50- NVDMCOPY :THE PANEL DOESN'T DISAPPEAR ESCAPING THE PROCEDURE 51- NVDM/2 SHOULD ACCEPT /B:C: AS WELL AS /B:C 52- THE COPY COMMANDS HAS TO BE CHANGED TO UPLOAD .PAN AND .TXT 53- PROBLEMS WITH NVDMBDSK 54- MIGRATION R.1 -> V.2 : PROCESS FAILURE DURING THE BIND 55- MIGRATION Q3 -> CLIENT : SOME PROBLEMS RUNNING ON GA CODE 56- INCORRECT PROCESSING OF LDU MANAGER ICON 57- MIGR.: THE SNA FILES ARE NOT CREATED MIGR.FROM Q2 TO Q4 58- BUILD:CMD FAILS WITH PROFILE BUILT FROM DIALOGS (WITH PARMS) 59- MIGR.:MORE FILES ARE NOT DELETED MIGR.FROM Q4 TO CLIENT 60- MIGRATION Q4 -> LDU : UNEXPECTED ERROR OCCURS CHANGING TDIR 61- ERROR MSG ANX1643 WHEN NVDMUFM IS ISSUED AND LU IS INACTIVE 62- PROBLEMS OCCUR MIGRATING FROM CLIENT TO LDU 63- CONNECTION REQUEST TO CC SERVER REJECTED AFTER REBOOT SERVER 64- KEYBOARD LOCKED WHEN ANY KEYS IS PRESSED AT CDM START OR STOP 65- LDU MANAGER GENERATES CORRUPTED PACKAGE FILES 66- LDU RECEIVER SHOULD USE SECONDARY ADAPTER 67- CDM DIALOG 68- ADDED LDU SAMPLE PACKAGE FILE OS2SE20.DFL 69- NVDMENV UTILITY INSTALLED BY NVDMCOPY WHEN CREATING PRODUCT IMAGES 70- DOC CHANGE (README.TXT), NVDMENV UTILITY INFORMATION 71- DOC CHANGE (README.TXT), INFORMATION ABOUT ON-LINE MANUALS DISTRIBUTED WITH CSD XR20276 72- DOC CHANGE (README.TXT), INFORMATION ABOUT CDM SAMPLE FILES, NOW IN ASCII FORMAT, DISTRIBUTED WITH CSD XR20276 73- HANG DURING CLIENT RE_INSTALLATION CHANGING DRIVE 74- WRONG CLIENT RE_INSTALLATION ON FAT SYSTEM 75- UNABLE TO START CORRECTLY 32 BIT APPLICATION 76- NVDM/2 VERSION 2 USES NOT APPROVED ICONS 77- RECEIVER USING SECONDARY ADAPTER DOCUMENTATION 78- DIALOG: IMPOSSILBLE TO WORK WHIT DIALOG WITH LAST BUILD 79- DOC: INCORRECT NETBIOS RESOURCES VALUES ON README TXT 80- ACTIVATE : WRONG CHANGE MANAGEMENT ON FAT CC CLIENTS 81- DELETE WS /F : N/A SNA REPORT CODE TO THE HOST 82- CDM LIST FAILED FOR LOG FILE OBJECTS 83- REMOTE DELETE: WRONG BEHAVIOUR IF THE RES. IS IN A CM STATUS 84- INSTALLATION: WRONG EXIT CODE IN CASE OF WRONG RSP KEYWORD 85- CDM BUILD:TRAPD DURING PACK WITH /IS OPTION 86- CDM BUILD: UNRECOVERABLE ERROR DURING PACK OF C:-OS2 DIR APAR PJ08280 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- REPORT NOT SENT AFTER ACTIVATE TO LARGE NUMBER OF NODES COMPONENT: ANXSNADS.EXE --------- PROBLEM SUMMARY: ---------------- After an activate for a group of nodes, the systems restarts and, thank to a procedure inserted in the startup.cmd, they try to send the report at host. Some of these nodes (end nodes) remains with the report in their queue even thougth the queue has status released. APAR PJ08321 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- MESSAGE ANX0432 LOOP AFTER CHANGING DATE FORWARD COMPONENT: ANXSNADS.EXE --------- PROBLEM SUMMARY: ---------------- Change the date of the workstation forward (for example 1993 instead of 1992), then send an object. When the date is restored, if you try to send an object, the message ANX0432 (duplicate sequence number) is displayed. APAR PJ08322 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- LDU DIST. MAIN PANEL NEW FIELD FILE PROCESSED COMPONENT: README.TXT --------- PROBLEM SUMMARY: ---------------- The field 'Files Processed' has been added beside the field 'File Sent' in the main panel of the LDU Distributor. PROBLEM SUMMARY: ---------------- The USER RESPONSE must be changed because the text refers to 'diskette A'. APAR PJ08405 PTF: XR20276 ========================= EXTERNAL SYMPTOM: ---------------- GLOBAL NAME NOT DISPLAYED IN ANX0090 AND ANX0099 COMPONENT: ANXCMSRV.EXE --------- PROBLEM SUMMARY: ---------------- When the message ANX0090 is issued: The characters %1 are displayed instead of the Global Name name. The same problem occurs with the message ANX0099: