************************************************************************ * Copyright (c) IBM Corporation 1991 - 1997 * * All rights reserved * * NetView DM/2 Version 2.1 * * FixPak XREFP03 * * Syslevel maintenance level XR00005 * ************************************************************************ ************************************************************************ * The following information provides more detail about the APARs fixed * * by this FixPak (XREFP03). * * * * CURRENT MAINTENANCE SYSLEVEL SERVICED IS: XR00005 * * * * NetView Distribution Manager/2 Version 2.1 * * * * NetView DM/2 V2.1 minimum maintenance level prerequisites: XR00002 * * * ************************************************************************ PTRNBR: 4U00524 APARNBR: PJ24373 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DISK CAMERA, ABNORMAL END MONITORING *.INI WITH LINE > 255 PROBLEM SUMMARY : The ANXWWTCM abnormal ends if any updated *.INI file contain lines greater than 255 characters. The error displayed is: ---------------------- ANXWWTCM An error occurred in your application. If you choose Ignore you should save your work in a new file If you choose Close, your application will terminate CLOSE IGNORE ----- ------ Reference: this failing occurrence was reported during the installation of DB2 V2.1 for Windows COMPONENTS CHANGED OR ENHANCED: ANXWWTCM.EXE NVDMWUPD.EXE PROBLEM CONCLUSION: The maximum length of a monitored ini line was increased up to 1024. PTRNBR: 4U00544 APARNBR: PJ24374 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DISK CAMERA SHOULD INCREASE MAXIMUM INI FILE SIZE PROBLEM SUMMARY : Installing some products,for instance Lotus Word Pro, some ini files can grow over 32k. In this case DiskCamera did not succeed in managing them showing correctly the message ANX1719. This limit should be enhanced to cover these products COMPONENTS CHANGED OR ENHANCED: ANXWWTCM.EXE PROBLEM CONCLUSION: The limit has been increased up to 50k. PTRNBR: 4U00588 APARNBR: PJ24375 PTFNBR: XREFP03 EXTERNAL SYMPTOM: AGENT DOS FAILS ACTIVATE IF THERE IS NO FLOPPY DRIVE PROBLEM SUMMARY : In case an ACTIVATE is requested for a machine that has no floppy drive installed, activate fails stating that it finds a diskette in the floppy drive. Following is message.dat: =========================================================== ** NetView DM/2 logged at 18:16:29 05/02/1996 ** ANX0148: (I) In drive A: there is a diskette inserted. =========================================================== ** NetView DM/2 logged at 18:16:30 05/02/1996 ** ANX0228: (E) The processing of the ACTIVATE request on workstation was unsuccessfully executed by the CDM Agent due to errors. =========================================================== COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE ANXCMPMC.EXE PROBLEM CONCLUSION: It was not thought as possible the case in which a machine has no floppy drive. Now a check is introduced and in case no floppy is present, no check is asked to understand if a diskette is inserted. PTRNBR: 4U00595 APARNBR: PJ24376 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDMUNIN FAILS TO UNINSTALL OS/2 CC CLIENT BECAUSE OF DB RELATED DLLS NOT FOUND PROBLEM SUMMARY : Trying to uninstall an OS/2 CC Client by using NVDMUNIN.EXE utility results as a failure with the message ANX8437 (The Database Manager DLLs can not be found). COMPONENTS CHANGED OR ENHANCED: NVDMUNIN.EXE PROBLEM CONCLUSION: The problem has been solved displaying the new warning message ANX8463 instead of message ANX8437 and the process continues. If message ANX8463 is caught while uninstalling an OS/2 CC Client, the User can disregard because CC Client does not use Database Manager. PTRNBR: 4U00608 APARNBR: PJ24377 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDMDTCT UTILITY DOESN'T RUN IF DB WAS NOT STARTED PROBLEM SUMMARY : When running NVDMDTCT utility, randomly, this does not detect that a NetView DM/2 V2.1 DB exists and so it fails to process the request. The problem occurs only if DataBase is not started before running NVDMDTCT. COMPONENTS CHANGED OR ENHANCED: NVDMDTCT.EXE PROBLEM CONCLUSION: The NVDMDTCT has been changed to run START/STOP DB MGR respectively before and after the process to drop NetView DM/2 database. PTRNBR: 4U00564 APARNBR: PJ24378 PTFNBR: XREFP03 EXTERNAL SYMPTOM: INCORRECT CHARACTERS ACCEPTED WHEN ADDING CLIENTS PROBLEM SUMMARY : The documentation for CDM ADDWS, states the all client names must start with an alphabetic character, but you are successful to add #CLIENT or $CLIENT: Is this an error in the code or the documentation ? COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The first character must be alphabetic. Code changed to comply design and related documentation. PTRNBR: 4U00577 APARNBR: PJ24379 PTFNBR: XREFP03 EXTERNAL SYMPTOM: STORED NAME MISSING IN THE REPORT SENT TO AS/400 PROBLEM SUMMARY : A resource that is already existing at the NvDM/2 node a for which the local file resides outside of the FSDATA is sent from AS/400 to the node. The operation is successful but the report sent from the node to the AS/400 doesn't contain the 09 stored name inside the 1538 structure. The AS/400 consider this field like a mandatory one and takes a format exception. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The problem was due to the fact that during a renewal when the operation was successful the to_be_stored string was blanked but the stored string was not set before. PTRNBR: 4U00589 APARNBR: PJ24380 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANXIFCOM.IFS IS NOT INSTALLED ON LAN MANAGER 2.0 PROBLEM SUMMARY : In some old version of Lan Manager, when this is installed on its OS/2 system (Microsoft Os/2 that is similar to OS/2 1.2), ANXIFCOM.IFS cannot be installed. In the same boot anxifcom.sys is installed Thus Netbios seems to be correctly installed. COMPONENTS CHANGED OR ENHANCED: ANXIFCOM.IFS PROBLEM CONCLUSION: This happens in those old Microsoft Os/2 systems where the function of Query Eas Size is not supported. In those cases the DosFSCtl returns an error that was considered unrecoverable. Now this case is correctly managed. PTRNBR: 4U00584 APARNBR: PJ24381 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANXSNADS TRAPS DURING STARTUP IF LMU2 IS STARTING TOO PROBLEM SUMMARY : During CDM START, at STARTUP.CMD processing time, Transmission Controller traps with the following registers: . System error = CDM Transmission controller SYS3175 A program has generated an access violation at 1bf8030c DOSCALL1.DLL 0001:0000030c P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000910 EBX=00004040 ECX=0000464f EDX=00000810 ESI=00000008 EDI=00000018 DS=464f DSACC=oof3 DSLIM=00000917 ES=464f ESACC=oof3 FSLIM=00000917 GS=0000 GSACC=**** GSLIM=******** CS:EIP=dfc6:0000030c CSACC=00db CSLIM=0000035f SS:EIP=0126:0000efe4 SSACC=ood3 SSLIM=0000efff EBP:0000eff0 FLG=00012202 . COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The analysis of the TRAP registers, that belong to doscall1.dll, showed that the TRAP occurred during a dossubset API call issued by ANXSNADS.EXE. The reason of the trap is that dossubset tries to expand a memory segment into a memory area already owned by another process. Before calling dossubset API, now, a preventive check is made to see if the memory is owned by other processes. PTRNBR: 4U00574 APARNBR: PJ24382 PTFNBR: XREFP03 EXTERNAL SYMPTOM: TRANSMISSION CONTROLLER (TC) ERROR INIT MESSAGES EVEN IF THE TC IS NORMALLY STARTED PROBLEM SUMMARY : By running the following scenario it occurs to catch some Transmission Controller (TC) error messages even if the TC is normally started. . SCENARIO OF THE FAILING EVENT . 1) submit a first plan sending a resource from host to NVDM/2 2) during the transmission stop the NVDM/2 server 3) hold the first plan 4) cdm start at the NVDM/2 server 5) submit a second plan from host and let it to complete 6) submit a third plan from host and let it to complete 7) submit a fourth plan from host and let it to complete 8) cdm stop at the NVDM/2 server 9) cdm start at the NVDM/2 server . At this time, looking at the CC Server, you realize that all NvDM/2 components are active, but the MESSAGE.DAT shows the following error messages: ANX0792 Error reading from transmission queue ANX0763 Transmission Controller error initialization ANX0601 Generic internal Transmission Controller error COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The issue of message ANX0792 is correct, because of the fact that after two message units the first one is considered lost and a CRMU with the status changed to terminated is sent related to the first message unit, while the other two messages were incorrectly issued, now fixed. PTRNBR: 4U00586 APARNBR: PJ24371 PTFNBR: XREFP03 EXTERNAL SYMPTOM: TRAP MAY OCCUR DURING AN ACTIVATE AT IPL TIME PROBLEM SUMMARY : By analyzing NetView DM/2 V2.1 code, we detected a latent problem with memory allocation during ACTIVATE at reboot that might results as a TRAP when moving files at IPL. The TRAP registers are not provided because not available. COMPONENTS CHANGED OR ENHANCED: ANXACTVD.DLL PROBLEM CONCLUSION: Corrected a memory allocation. PTRNBR: 4U00578 APARNBR: PJ21326 PTFNBR: XREFP03 EXTERNAL SYMPTOM: REQUIREMENT TO SUPPORT SLOVENIA, YUGOSLAVIA THAILAND CODEPAGES PROBLEM SUMMARY : This APAR to have NetView DM/2 V2.1 to support Slovenia, Yugoslavia and Thailand codepages. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL ANXBFTH.DLL ANXLBFS.DLL ANXEFAPI.DLL PROBLEM CONCLUSION: Added support for Slovenia, Yugoslavia and Thailand. PTRNBR: 2M04142 APARNBR: PJ22107 PTFNBR: XREFP03 EXTERNAL SYMPTOM: CATALOG PERF. IN ASYNCRON WAY IN DIFFERENT SESSIONS PROBLEM SUMMARY : Attempting to run multiple concurrent CDM CATALOG, on different OS/2 sessions, ANX0310 (catalog entry already exist) is wrongly issued and the object is not cataloged. . SAMPLE SCENARIO TO VERIFY: . 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 . COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL ANXCSCD3.BND PROBLEM CONCLUSION: Changed the internal process to synchronize multiple concurrent CDM CATALOG. PTRNBR: 4U00565 APARNBR: PJ22107 PTFNBR: XREFP03 EXTERNAL SYMPTOM: FITTING PTR 2M04142 (DISTRIBUTED W APAR PJ14863) ON V2.1 PROBLEM SUMMARY : This APAR to fit APAR PJ14863 on Netview DM/2 V2.1 . . References: PMR 0997X B108 C760 APAR PJ14863, opened against version 2.0 APAR PJ22107, opened against version 2.1 COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL ANXCSCD3.BND PROBLEM CONCLUSION: Fitted APAR as requested. PTRNBR: 4U00568 APARNBR: PJ22187 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ADDS DUPLICATE ENTRIES IN CONFIG.SYS PROBLEM SUMMARY : The NVDMUPO adds duplicate entries into CONFIG.SYS room, while processing an UpdateStatement verb into a MOD file, if the token to add ends with semicolon. References: PMR 8E667 B057 C649 APAR PJ22187 COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE PROBLEM CONCLUSION: Corrected the process to add a token. PTRNBR: 4U00567 APARNBR: PJ22197 PTFNBR: XREFP03 EXTERNAL SYMPTOM: TIMING PROBLEM SUBMITTING AN INITIATE PROCEDURE PROBLEM SUMMARY : Submitting several initiate procedures for the same procedure, randomly, the messages ANX0211 (unrecoverable error) and ANX0074 (Change Controller ended because of errors) are logged in the message.dat. . The related error entry is: . ================================================================ ¡ ** NetView DM/2 logged at 20:04:11 16/12/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPZC. Additional Data : 41 4e 58 41 43 50 5a 43 31 31 00 00 41 4e 58 43 ANXACPZC11..ANXC 53 50 46 36 53 45 41 52 43 48 20 46 52 4f 4d 20 SPF6SEARCH FROM 46 49 4c 45 08 00 1c 00 20 00 00 00 00 00 00 00 FILE.... ....... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 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: ANXCMSRV.EXE PROBLEM CONCLUSION: The problem was due to the fact that the initiated procedure resulted locked by other process. Now, a retry loop of five attempts is performed before to return with error. PTRNBR: 4U00570 APARNBR: PJ22267 PTFNBR: XREFP03 EXTERNAL SYMPTOM: RC=37 ON CDM DELETEIT WHEN INITIATING A PROCEDURE PROBLEM SUMMARY : Getting RC 37 when initiating a procedure to delete a target directory for component name CPOP.CONF.MIC2.FQAPPL . The name of our procedure is CPOP.CONF.MIC2.FQAPPL.FQVC18.5100 and it fails with return code 37 executing the following statement: CDM DELETEIT CPOP.CONF.MIC2.FQAPPL. Changing the name of the procedure to CPOP.CONF.MIC2.FQTEMP it does work properly. . Reference: PMR A0372 BM18 C649 COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: When executing a CDM DELETEIT, a check is done on the entries of the database in order to verify what is the status of the object. The status must be CATALOGED; only in this case the CDM DELETEIT is allowed. Initiating a procedure that fit all token of a given GROUP ID set the status of the procedure to SCHE. In the specific case described the procedure name fits the GROUP ID for which is requested the DELETEIT and this resulted as error 37. Now, a check has been added to verify, when the status is different from CATALOGED, the object type; if the object type is PROC, the entry is not considered as locked. PTRNBR: 4U00569 APARNBR: PJ22290 PTFNBR: XREFP03 EXTERNAL SYMPTOM: MEMORY NOT RELEASED WHEN INSTALLING ON CC CLIENTS PROBLEM SUMMARY : Submitting an Install against NetView DM/2 CC Client, the Change Controller acquires two memory segments that are not released after the request is submitted to the CC Client. . This behavior causes memory leakage when running on OS/2 Warp because of the new memory model: 4K instead of 64K. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The allocated memory is now released when no longer needed. PTRNBR: 4U00571 APARNBR: PJ22306 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NETVIEW DM/2 V2.1 OS2 CC AGENT FAILS TO RUN SOME WINDOWS APPLICATIONS PROBLEM SUMMARY : Some Windows applications are not recognized as Windows exe files by CDM Agent that considers those as OS/2 exe ones; this causes CDM Agent to fail their execution. An example of these application is a Software Installer used to CID install application on Windows 3.1 or WINOS2. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: To determine what kind of EXE CDM Agent is requested to execute, a call to DosQAppType API is done. This API returned values 0x400 and 0x300 for Windows application type that were not managed, now corrected. PTRNBR: 4U00572 APARNBR: PJ22361 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DATETIME NOT CORRECTLY PROCESSED FOR REMOTE REQUESTS PROBLEM SUMMARY : Submitting from a R.A. to a server an Activate function for a group of CC Clients, with the SDT and DT parameters, the STD (submission datetime) is correctly processed while the /DT (execution datetime) does not. Half of the CC Clients Activate are started immediately and not at the desired datetime. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Corrected the EXECUTION DATE process. PTRNBR: 4U00576 APARNBR: PJ22606 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DETAILS IN THE MESSAGE.DAT DURING THE QUEUE RECOVERY PROBLEM SUMMARY : Sometime the transmission controller queue recovery can take some time if for example there are a lot of transmissions in progress. This can lead the user to think that the CDM start command is hanging. This ptr is in order to detail the progress done by the Transmission Controller during the queue recovery. COMPONENTS CHANGED OR ENHANCED: ANX.MSG ANXSNADS.EXE PROBLEM CONCLUSION: Some messages were added in order to detail the queue recovery process. PTRNBR: 4U00579 APARNBR: PJ22687 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NO REMOTE DESTINATION TARGETS FROM DIALOG WITH NETVIEW DM/2 REMOTE ADMINISTRATOR AT XREFP02 PROBLEM SUMMARY : When trying to install packages from CDM dialogs on the Remote Administrator Workstation, remote targets does not appear as available targets. This occurs when selecting one packages. If more than one package is selected, remote targets are showed as available for installation. No difference using Force or No-Force. References: PMR 1695X B180 C846 APAR PJ22687 COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL ANXCSCDP.BND PROBLEM CONCLUSION: The behavior claimed by Customers was due to a wrong SQL select, now corrected, operated against NetView DM/2 V2.1 DB tables to retrieve possible local or remote targets to install only one object. PTRNBR: 4U00580 APARNBR: PJ22774 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDM/2 AGENT TRAPS IN CASE OF CORRUPTED PACKAGES PROBLEM SUMMARY : In case of an installation of a corrupted package, that is a package that has some bytes different from the original one built by the product, the agent does not recognize that the package is invalid. As a consequence a trap may happen; in this case registers are ANXCKPUQ.DLL 0007:0c65e8a7 p1=00000000 p2=ffffffff p3=xxxxxxxx p4=xxxxxxxx eax=0000003f ebx=00000000 ecx=0008f1a4 edx=0016dd70 esi=00000008 edi=0000dd70 ds=7e17 dsacc=00f3 dslim=00000c03 es=7e37 esacc=00f3 eslim=0000d534 fs=150b fsacc=00f3 fslim=00000030 gs=0000 gsacc=**** gslim=******** cs:eip=cb0f:00000bad csacc=00fb cslim=00000a5f ss:eip=0077:0000f19e ssacc=00f3 sslim=0000ffff ebp=0000f5fe flg=00012a96 Other times, the consequence is an that the NetView DM/2 Agent hangs up. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: A cycle of unpacking did not return anything in case a corruption has detected. Now it does. PTRNBR: 4U00582 APARNBR: PJ22942 PTFNBR: XREFP03 EXTERNAL SYMPTOM: INCORRECT MESSAGES SEQUENCE AFTER A NEGATIVE ACCEPT PROBLEM SUMMARY : When executing a CDM ACCEPT of a given resource for which was accidentally erased the related *.REM file, an incorrect and misleading sequence of messages are logged into message dat. This sequence starts, correctly, with message ANX0220 but continues wrongly with messages ANX0211 and ANX0054. In fact, even if the ANX0211 is logged, the Change Controller does not end but however the CDM ACCEPPT does not complete successfully as per message ANX0054. This sequence to be improved avoiding the ANX0211 issue and changing ANX0054 with ANX0059. Reference: PMR 4667E B180 C000 COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The accidental user deletion of .REM file was not managed since the design activity. Now this condition is treated in a proper way as expected: see section PROBLEM SUMMARY. PTRNBR: 4U00583 APARNBR: PJ23115 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANXCMSRV.EXE TRAP IF EMPTY FILE ARRIVES WITH 153B PROBLEM SUMMARY : Sending an empty file, from NetView DM/MVS to NetView DM/2 V2.1, this last at XR00002 up to XR00004 maintenance level, results as a TRAP as in the following example: . 05-28-1996 14:02:16 SYS3175 PID 7e30 C:½IBMNVDM2½BIN½ANXCMSRV.EXE c0000005 00054d57 P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=0000000d EBX=0000000d ECX=00000006 EDX=00000000 ESI=00000000 EDI=00000000 DS=01b7 DSACC=00f3 DSLIM=0000fef7 ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=002f:00004d57 CSACC=00fb CSLIM=0000f3ee SS:ESP=07f7:0000df10 SSACC=00f3 SSLIM=0000f9ff EBP=0000df2a FLG=00012246 ANXCMSRV.EXE 0005:00004d57xr20466 COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: If a file is empty and 153b structure is presence, NvDM/2 now accepts the distribution. PTRNBR: 4U00600 APARNBR: PJ23142 PTFNBR: XREFP03 EXTERNAL SYMPTOM: RETRIEVE FAILS IF ANY GLOBALNAME IS EQUAL TO 16 CHAR/DIGIT PROBLEM SUMMARY : The message ANX1005 is prompted issuing a CDM RETRIEVE even if the global name is equal to 16 characters. References: PMR 0625X B048 C724 COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Corrected the global name token management. PTRNBR: 4U00587 APARNBR: PJ23144 PTFNBR: XREFP03 EXTERNAL SYMPTOM: TRAP ON ANXCMCLC.EXE PROCESSING AN INSTALL FUNCTION PROBLEM SUMMARY : During a distribution to 2500 workstations,the module ANXCMCLC.EXE traps at location 00020a44. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE PROBLEM CONCLUSION: The problem has been solved by removing an fclose of a file no longer accessed. PTRNBR: 4U00612 APARNBR: PJ24229 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DIALOGS DOES NOT HANDLE AM/PM INTO MESSAGE/ERROR DAT PROBLEM SUMMARY : The timestamp is not displayed into the CDM Local Message or Error Log windows when message or error log entries, into respectively MESSAGE or ERROR dat files, are expressed in 12H clock style (ie. with AM or PM suffix). . Reference: PMR 14332 B111 C000 APAR PJ24229 COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Corrected the parsing process of either NetView DM/2 V2.1 MESSAGE and ERROR dat files to fill related CDM Dialogs windows (ie. Local Message log and Local Error Log). PTRNBR: 4U00610 APARNBR: PJ24272 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDM/6K DETECTS A FORMAT ERROR FOR DATETIME INSTALL PROBLEM SUMMARY : Submitting an install for a NvDM/6k to a NvDM/2 CC Server having specified the datetime option, NvDM/6k detects a format error when it receives the send-delay-report from NvDM/2 node because of structure 88 in the 1573 (agent object) is missing. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The structure 88 (global name related to cm request) has been now inserted inside send-delay-report for datetime install. PTRNBR: 4U00611 APARNBR: PJ24188 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANX0082 AT NvDM2 AND NDM0856E AT NvDM/MVS DURING STRESS PROBLEM SUMMARY : During a very massive distribution, randomly for some resources, NvDM2 specific server fails with ANX0082 message. . Hereafter the log entries at both NvDM/MVS and NvDM/2 sites: . 96/01/12 01:36:44 NDM0856E AN AGENT EXCEPTION WAS DETECTED WHILE PROCESSING RESOURCE aaa.bbb.cccc, PLAN Q1111111, PHASE SENDRES, FUNCTION SEN FLAT, NODE IC81260Z, LOGICAL UNIT IC8126 LOGMODE PCNNDMH, SNA REPORT CODE 085C0001. . ** NetView DM/2 logged at 01:20:35 12/01/1996 ** ANX0082: (E) A request has not been processed because the SNA/FS ** NetView DM/2 logged at 01:20:35 12/01/1996 ** ANX0082: (E) A request has not been processed because the SNA/FS Server detected an error. **************************************************************** ** NetView DM/2 logged at 01:20:37 12/01/1996 ** ANX0074: (E) The Change Controller ended because of errors. error messages in NDM/2 ERROR log: ** NetView DM/2 logged at 01:20:35 12/01/1996 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXBFP23. Return codes were:Primary=20,Secondary=32,Auxiliary=0. Additional Data : 41 4e 58 42 46 50 32 33 30 30 30 32 eb 10 0f 41 ANXBFP230002 4e 58 42 46 00 00 45 52 06 00 45 52 52 4f 52 20 NXBF..ER..ERR 46 52 4f 4d 20 44 45 4c 45 54 14 00 20 00 FROM DELET.. **************************************************************** COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The error depends on a sys32 (access violation...) when NvDM/2 transform handler attempts to delete its temporary files. This problem occurs only on very speed machine under very stressing conditions, so it is a timing related one. Now, the case in which a sys32 (access violation...) is caught while deleting a temporary file is managed in a different way: instead to exit as soon as sys32 is found, now transform handler attempts a number of times to delete that file and exits with error only if all those attempts failed. Also, the logging was improved too. PTRNBR: 4U00594 APARNBR: PJ23934 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NetView DM/2 HANGS DURING MASSIVE DISTRIBUTION PROBLEM SUMMARY : When a massive distribution is addressed from a NvDM Host to a NvDM2 CC Server, at a certain point the CC Server hangs. The distribution consists in several SEND, several INSTALL, several INITIATE of procedures that issue CDM commands like: CDM INSTALL, CDM BUILD, CDM DELETE. When the hang take place, the plan at host remains pending while at node site we see that several requests remain in <in progress status>, no more cmf* and .cli and .tmp file management is performed by NetView DM/2 V2.1 Change Controller and Transmission Controller (TC) queues show release status with any or none entry. The CDM status shows, when this command doesn't hang too, all components in active status, the error.dat and message.dat show nothing since the last completed operation. The only way to recover is to issue a CDM stop, when it runs, or to reboot the machine. The analysis of a system dump, shows that all NvDM/2 threads are blocked on ram or system semaphores. What relevant is that 2 or more anxsnads.exe threads are blocked on the same ram semaphore this means that the are going to access the same .sna file. If CDM traces are activated,the problem never occurs,so it looks to be a timing problem. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: There was a logic error accessing .SNA files thru a semaphore vector's index defined like a global variable so that there was the possibility to have this value unpredictably changed. Now the vector index is managed in a different way. PTRNBR: 4U00591 APARNBR: PJ23224 PTFNBR: XREFP03 EXTERNAL SYMPTOM: LISTWS SHOWS SOME CC CLIENTS AS INACTIVE WHILE THEY ARE NOT PROBLEM SUMMARY : CDM LISTWS sometimes give a wrong result saying that some ws are not active while they result active. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: In some cases NetBIOS seems not to work properly and returns back the buffer used for fnd_status as it was passed to NetBIOS itself. Thus, if buffer is dirty, dirty values are returned. Here the buffer is cleaned before passing it to NetBIOS and thus we can evaluate it better. PTRNBR: 4U00592 APARNBR: PJ23423 PTFNBR: XREFP03 EXTERNAL SYMPTOM: DOS PRISTINE, CLIENTS REPORTED INVALID HANDLE PROBLEM SUMMARY : When more than three pristine DOS machines run at the same time, it is easy to have clients ending without installing all packages. Looking inside error.dat or related install log files, problems related to the writing or reading of a file are highlighted. Message.dat may also report some I/O error , while error.dat may have entries with auxiliary code = 6 (invalid handle). COMPONENTS CHANGED OR ENHANCED: ANXIFSRV.EXE PROBLEM CONCLUSION: To prevent thus behavior, a check has been introduced to verify that a file to be closed has been previously opened by the same client. PTRNBR: 4U00596 APARNBR: PJ23603 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDMINST HANGS AFTER HAD ACCESSED STARTUP.CMD PROBLEM SUMMARY : The NetView DM/2 V2.1 CC Server installation, by using NVDMINST, hangs after has accessed STARTUP.CMD that is the last message logged into ANXINST.LOG . Reference : PMR 7394X B342 C758 COMPONENTS CHANGED OR ENHANCED: SBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION: The hanging of NVDMINST was due to DB2 that did not return the control when requested to execute STOPDBM. However, we investigated that STOPDBM is not really needed at the end of installation and so we removed that instruction while inserting a new message that advises the NetView DM/2 installation is terminating. PTRNBR: 4U00597 APARNBR: PJ23639 PTFNBR: XREFP03 EXTERNAL SYMPTOM: INCORRECT OUTPUT OF COMMAND CDM LIST /WS PROBLEM SUMMARY : Running CDM LIST * /WS:‡WS.LST, it run OK. However, when running CDM LIST * /WS, sometimes it run OK, but, randomly, it does not return the CM status. Reference : PMR 1863X B100 C838 COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Corrected the initialization of the request block to store CDM LIST output. PTRNBR: 4U00593 APARNBR: PJ23664 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NVDM(R/B)DSK ENHANCEMENT TO SUPPORT 2+ BOOT DSKS PROBLEM SUMMARY : Starting from OS/2 Warp Version 4, the boot diskettes to IPL change from 2 to 3 therefore NVDMBDSK/NVDMRDSK fails to produce Pristine diskettes set because designed to handle 2 boot diskettes. In particular, the NVDMBDSK/NVDMRDSK fail because of CONFIG.SYS is not present on the last diskette of the new OS boot set, that to which are made the changes to support NetView DM/2 Pristine. The CONFIG.SYS is present on the diskette 1. COMPONENTS CHANGED OR ENHANCED: NVDMBDSK.EXE NVDMRDSK.EXE PROBLEM CONCLUSION: The NVDMBDSK utility has been changed to prompt a pop-up message to request User to insert boot diskette with CONFIG.SYS before to continue the process. Also, the NVDMRDSK has been changed to pop up a message to ask for diskette with CONFIG.SYS inserted into the drive when needed to update CONFIG.SYS file. PTRNBR: 4U00599 APARNBR: PJ23710 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANXIFCOM CAUSES AN HANG IN CASE OF MULTIPLE DEVICES PROBLEM SUMMARY : In case of multiple device drivers installed, anxifcom.ifs sometimes hangs, blocking completely the machine after some work has been done. In some cases it hangs also at boot time COMPONENTS CHANGED OR ENHANCED: ANXIFCOM.IFS PROBLEM CONCLUSION: This problem was due to memory management process, now changed. PTRNBR: 4U00602 APARNBR: PJ23722 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANX0166 AT CDM SEND IF CHANGE FILE BUILT FROM A: DRIVE PROBLEM SUMMARY : CDM SEND fails if the local file related to the global name to be sent has been created via CDM BUILD command having a: drive as source drive. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Correct the CDM BUILD process that was causing the failure. PTRNBR: 4U00601 APARNBR: PJ23723 PTFNBR: XREFP03 EXTERNAL SYMPTOM: INCORRET ATTRIBUTE CREATING CONFIG.NDM AFTER ACTIVATE PROBLEM SUMMARY : Submitting a cdm activate, if config.ndm doesn't exist, it is created with wrong attributes. In this case the next CDM ACTIVATE doesn't works fine. References : PMR 7795X B200 C838 COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE ANXACTVD.DLL ANXACTVF.SYS PROBLEM CONCLUSION: Corrected the way to call DosQFileMode API in order to have the working CONFIG.NDM file to have the same attributes of the CONFIG.SYS file. PTRNBR: 4U00604 APARNBR: PJ23878 PTFNBR: XREFP03 EXTERNAL SYMPTOM: ANX1247 RUNNING CDM BUILD PROBLEM SUMMARY : Running CDM BUILD from a READ ONLY current path such as a CD-ROM, protected diskette, remote resource accessed in read only, etc. results as getting message ANX1247. LOCAL FIX: Circumvention consists in running CDM BUILD command from a READ/WRITE current path such as a HARD DISK for instance. References: PMR 6348X B689 C864 APAR PJ23878 COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: Corrected the management of the TEMPORARY DIRECTORY used to prepare Change File. Now, the Temporary Directory is created below the path name specified for the Change File to build. PTRNBR: 4U00605 APARNBR: PJ23936 PTFNBR: XREFP03 EXTERNAL SYMPTOM: 084C0002 SENSE CODE WHEN SENDING A RESOURCE TO A CC SERVER WITH MORE THAN 4Gb FREE DISK STORAGE PROBLEM SUMMARY : Remote Send from NvDM/6000 RA to DM/2 CC Server results in SNA sense code 084C0002 that means receiver is unable to create specified data object as a result of an insufficient disk storage condition that occurred at allocation time. This only occurs when the amount of Free Disk Space is greater than 4 Gb . COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: Correct the process to calculate the free disk storage on target WS. PTRNBR: 4U00607 APARNBR: PJ24049 PTFNBR: XREFP03 EXTERNAL SYMPTOM: NETVIEW DM/2 V2.1 INSTALLATION PROGRAMS DELETE START STATEMENTS INTO STATUP.CMD FILE PROBLEM SUMMARY : When installing/reinstalling/configurating NetView DM/2 V2.1 the related installation programs deletes statements into STARTUP.CMD that start with "START C... or start c..." as in following examples: start c:½my.cmd START C:½MYDIR½APPL.CMD References: PMR 05032 B089 C724 APAR PJ24049 COMPONENTS CHANGED OR ENHANCED: SBODY.EXE PMSBODY.EXE PROBLEM CONCLUSION: The incorrect processing was due to the string 'START CM' verified into the STARTUP.CMD when the NetView DM/2 V2.1 installation program is requested to update such file (ie. the switch /NOSTARTUP is not passed along with other parameters to NVDMINST). Now, the verification is performed with a string such as 'START CM ' that make unique the statement to check. PTRNBR: PJ22425 APARNBR: PJ22425 PTFNBR: XREFP03 EXTERNAL SYMPTOM: REQUIREMENT FOR DOUBLE QUOTES AROUND PARAMETERS IN NVDM2 PROFILE PROBLEM SUMMARY : When product installation programs require parameters with quotation marks, NVDM2 requires a second set of quotation marks around the entire parameter. This is not explained in the NVDM2 documentation. COMPONENTS CHANGED OR ENHANCED: README.TXT PROBLEM CONCLUSION: Amended NetView DM/2 V2.1 CDM User's guide, via README.TXT, as suggested. PTRNBR: 1000096 APARNBR: PJ23714 PTFNBR: XREFP03 EXTERNAL SYMPTOM: LDSR DOES NOT CONNECT LOGGING JUST EMPTY BYTES PROBLEM SUMMARY : Sometimes LDSR does not connect displaying message LDR0017 - no more NetBIOS sessions available. On LDSR.LOG appears the message and a 4 lines of dump with all characters equal to 0. NetBIOS resources results enough when checked with tools, such for instance TESTNB. COMPONENTS CHANGED OR ENHANCED: LDSR.EXE PROBLEM CONCLUSION: Here, we had the result of two different conditions. - the first is that the possibility to have no listen command on the server was not considered - the second is that the NCB was not saved in case of unpredictable return code.. Now both situations are managed. PTRNBR: 4U00616 APARNBR: PJ24410 PTFNBR: XREFP03 EXTERNAL SYMPTOM: TRAP ISSUING A REMOTE INITIATE WITH PARMS WHEN RUNNING COMMUNICATIONS SERVER V4.X AND NETVIEW DM/2 V2.1 PROBLEM SUMMARY : Issuing a remote initiate against a CC Client attached to a CC Server a TRAP occurs if: - on cc-server is running Comm. Server (4.0 or 4.1) - in the initiate request are specified some parameters . The trap registers are: . 01-09-1997 17:57:25 SYS3171 PID 0085 D:½IBMNVDM2½BIN½ANXCMSRV.EXE c0000005 1f4127e2 P1=00000002 P2=011aff00 P3=XXXXXXXX P4=XXXXXXXX EAX=011b0623 EBX=011b0608 ECX=011b009c EDX=000001f4 ESI=010dab5f EDI=108606ab DS=0053 DSACC=d0f3 DSLIM=1fffffff ES=0053 ESACC=d0f3 ESLIM=1fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:1f4127e2 CSACC=d0df CSLIM=1fffffff SS:ESP=0053:011aff04 SSACC=d0f3 SSLIM=1fffffff EBP=011b00d4 FLG=00012202 . ACSGCBLD.DLL 0001:000027e2 ====================================================== If CS/2 apar JR10096 is applied a different trap occurs: . D:½IBMNVDM2½BIN½ANXCMSRV.EXE c0000005 1f4727f2 P1=00000002 P2=011aff00 P3=XXXXXXXX P4=XXXXXXXX EAX=011b0623 EBX=011b0608 ECX=011b009c EDX=000001f4 ESI=010d0684 EDI=140d067a DS=0053 DSACC=d0f3 DSLIM=1fffffff ES=0053 ESACC=d0f3 ESLIM=1fffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:1f4727f2 CSACC=d0df CSLIM=1fffffff SS:ESP=0053:011aff04 SSACC=d0f3 SSLIM=1fffffff EBP=011b00d4 FLG=00012202 . ACSGCBLD.DLL 0001:000027f2 . As appears in trap registers, even if the trap originator is ANXCMSRV.EXE we are inside 32 bit code belonging to ACSGCBLD.DLL . COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: . The analysis carried out by Communications Server C/T lead that the reason of the TRAP is that when we CALL ACSGCBLD.DLL to invoke GET_CP_CONVERT_TABLE function, we have not enough stack space, now increased. ************************************************************************ * The following information provides details about the APARs fixed by * * previous FixPaks cumulated in this current FixPak issue * * * * Netview Distribution Manager/2 Version 2.1 * * * ************************************************************************ PTRNBR: 1000095 APARNBR: PJ21275 PTFNBR: XREFP02 EXTERNAL SYMPTOM: LDU MAP DISTRIBUTOR FILE HAS A MAXIMUM SIZE THAT SOMETIMES IS NO MORE SUFFICIENT PROBLEM SUMMARY : . Reference: PMR 7492X B469 C000 . Due to the increasing complexity and to increasing number of products that form an entire software environment, it is sometimes not possible to clone an entire machine using a distributor map file limited to 20 K in size COMPONENTS CHANGED OR ENHANCED: LDS.EXE PROBLEM CONCLUSION: The limit of the size of distributor map file has been enhanced up to 40 k. PTRNBR: 2M04205 APARNBR: PJ21862 PTFNBR: XREFP02 EXTERNAL SYMPTOM: SWAPPER.DAT FILE GROWS USING CDM RELEASE PROBLEM SUMMARY : . Reference: PMR 2X184 B073 C649 . When the a TC queue is in HELD or Temporary Held while the associated link is down, running CDM RELEASE to release a given remote destination queue, the system accumulates memory and the swapper.dat file grows. COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: The problem was due to a wrong usage of APPC Display verb. With this verb the Data Buffer is not deallocated by CM/2 until the associated TP (Transmission controller) is stopped. Corrected the call to APPC verb. PTRNBR: 2M04212 APARNBR: PJ21258 PTFNBR: XREFP02 EXTERNAL SYMPTOM: PROBLEM ON REPORT WHEN IT IS SENT A 00:00:00 TIME PROBLEM SUMMARY : . The execution of a Change Management request (for instance an Install function) causes problems if the report of the request is generated at the time 00:00:00. . In particular, in this condition the function fails with the messages: ================================================================ ** NetView DM/2 logged at 00:00:00 (AM) 11-11-1995 ** ANX0211: (E) An unrecoverable error prevents continuation of processing. ================================================================ ** NetView DM/2 logged at 00:01:17 (AM) 11-11-1995 ** ANX0074: (E) The Change Controller ended because of errors. ================================================================ and the error.log: ================================================================ ** NetView DM/2 logged at 00:00:00 (AM) 11-11-1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXAFPPR. Additional Data : 41 4e 58 41 46 50 50 52 30 30 30 33 c5 c1 e7 c4 ANXAFPPR0003..¡. e2 d7 c4 40 18 00 00 00 00 00 00 00 58 b3 e7 75 œ].‡........X¡¡u c5 04 c5 d5 c1 c7 40 40 40 40 01 00 00 00 00 00 .....ñ‡‡‡‡...... 00 00 00 00 01 00 00 00 03 00 28 00 00 00 00 00 .........(..... 00 00 00 00 00 00 00 00 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: ANXLASD.DLL PROBLEM CONCLUSION: Correct the management of any report generated at 00:00:00 . PTRNBR: 4U00430 APARNBR: PJ21860 PTFNBR: XREFP02 EXTERNAL SYMPTOM: WIN.INI FILE IS NOT MONITORED IF LOCATED OUT OF WINOS2 OR WINJOS2 SUBDIRECTORY PROBLEM SUMMARY : Disk Camera is not able to monitor windows applications under OS/2 J because of the different name of WINOS2 dir. . Reference PMR: 0916X B613 C760 . COMPONENTS CHANGED OR ENHANCED: NVDMPRE.EXE NVDMPOST.EXE NVDMUPO.EXE PROBLEM CONCLUSION: Changed the way to locate WIN.INI, PROGMAN.INI and SYSTEM.INI . Previously this change, the above files were tried to locate under a hardcoded path such as: <boot_drive>\OS2\MDOS\WINOS2 . With this change, the above files are located along the paths specified into the global environment variable PATH; the first occurrence for each file is taken as valid. PTRNBR: 4U00481 APARNBR: PJ21861 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DISKCAMERA FOR OS/2 FAILS TO MONITOR WIN.INI BECAUSE CUSTOMER USED A CUSTOMIZED NAME FOR WINOS2 SUBDIRECTORY AS OS/2 ALLOWS. PROBLEM SUMMARY : . Reference PMR: 8X633 B370 C000 . The OS/2 V3.X let you the option to define your own directory to store the files to support Windows and so also the related INI files such as WIN.INI, SYSTEM.INI and PROGRAM.INI . The NVDMPRE and the companion NVDMPOST are not able to monitor the above mentioned file, for any change, if located out of <boot_drive>\OS2\MDOS\WINOS2 path. COMPONENTS CHANGED OR ENHANCED: NVDMPRE.EXE NVDMPOST.EXE NVDMUPO.EXE PROBLEM CONCLUSION: This problem was fixed with PTR 4U00430 distributed starting from FixPak XREFP02: refer to APAR PJ21860. PTRNBR: 4U00488 APARNBR: PJ20560 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CDM DIALOG ISSUES MESSAGE ANXE5141 ON 2ND INSTALL OF AN OBJECT PROBLEM SUMMARY : Once a change object has been installed in INRU status on a workstation in the CC domain, it is no more possible to install the same object on any other workstations via CDM dialogs: as soon as the specific change object has been selected and the <Selected/Install> command is invoked, the message ANXE5141 is displayed and the <Install> dialog is not opened. The occurrence does not exist executing the task by command line. COMPONENTS CHANGED OR ENHANCED: ANXDBSRV.DLL PROBLEM CONCLUSION: The problem, now corrected, was due to a wrong workstation list returned from NetView DM/2 database services to the CDM Dialog. PTRNBR: 4U00493 APARNBR: PJ21864 PTFNBR: XREFP02 EXTERNAL SYMPTOM: ALIGNMENT WITH NEW CID ARCHITECTURE ENABLEMENT SPECIFICATION PROBLEM SUMMARY : The new CID Enablement Specification recommends a new meaning and action for SDM (Software Distribution Manager) agent. COMPONENTS CHANGED OR ENHANCED: ANXCMCLC.EXE ANXCMCLS.EXE PROBLEM CONCLUSION: The Return Codes are now managed according with the new spec. PTRNBR: 4U00497 APARNBR: PJ21865 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CLIENT IN 'RUNNING' STATUS FOREVER WHEN EXECUTING AN INSTALL PROBLEM SUMMARY : The problem occurs randomly trying to execute an INSTALL of Change File that was built via CDM BUILD command with the compress option (/T). In this case it is possible that the client remains in 'Running' status forever and the install remains in pending. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: Due to a lack of initialization of a table the pack/unpack function loops into the uncompress routine and never exit from this check. PTRNBR: 4U00502 APARNBR: PJ21866 PTFNBR: XREFP02 EXTERNAL SYMPTOM: ERROR LOG NOT MEANINGFUL FOR PACK/UNPACK FAILURE PROBLEM SUMMARY : When an error >8 is returned fro pack/unpack the related log into the error.dat is not meaningful because no return code, returned from the failing function, is recorded as auxiliary code. COMPONENTS CHANGED OR ENHANCED: ANXCMCLT.EXE PROBLEM CONCLUSION: Improved error data to log. PTRNBR: 4U00506 APARNBR: PJ21867 PTFNBR: XREFP02 EXTERNAL SYMPTOM: WRONG MESSAGE, ANX0250, ISSUED WHEN A FILE IS DETECTED LOCKED DURING AN INSTALL PROBLEM SUMMARY : Wrong message ANX0250 (I/O error) is issued instead of ANX0145 (file in use) when a file is locked during an install. COMPONENTS CHANGED OR ENHANCED: ANXCKPUQ.DLL PROBLEM CONCLUSION: The wrong issue of the message ANX0250 was due to an invalid RC was returned when trying to open the target file, now corrected. PTRNBR: 4U00508 APARNBR: PJ21868 PTFNBR: XREFP02 EXTERNAL SYMPTOM: NVDMUPO DOES NOT MANAGE CORRECTLY COMMA IN AFTER ATTRIBUTE PROBLEM SUMMARY : NVDMUPO does not manage correctly AddStatement verb in modification file that have AFTER: attribute with the first value containing a comma. . For example, a modification file as : . îWIN.INI® AddStatement(BOTTOM,<îPostScript,LPT1.OS2®>) AddStatement(AFTER:îPostScript,LPT1.OS2®,<MYAPPL=TEST>) . once processed by NVDMUPO, updates WIN.INI file as follows: . îWIN.INI® îPostScript,LPT1.OS2® <--- this is appended at the bottom LPT1.OS2®MYAPPL=TEST | <-------| these are characters not desired COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE README.TXT PROBLEM CONCLUSION: The OS/2 Camera has been enhanced in order to manage value1, of the AFTER: attribute, that contain a comma. . This enhancement has been reached introducing a new grammatical for value1 of the AFTER: attribute in order to manage comma; the syntax remain unchanged as follows: . verb(attribute:value1,value2) . The new grammatical to have correctly handled comma in value1 is to substitute comma with '&comma' (without quotes) key. . For instance, assuming to have a statement such as: . AddStatement(AFTER:îA,B®,<SOFTFONT1=$(TargetDir)PSFONTS>) . the above statement should be changed as follows: . AddStatement(AFTER:<îA&commaB®>,<SOFTFONT1=$(TargetDir)PSFONTS>) PTRNBR: 4U00509 APARNBR: PJ21869 PTFNBR: XREFP02 EXTERNAL SYMPTOM: TRAP IN ANXCMSRV AFTER INSTALLING A CHANGE FILE PROBLEM SUMMARY : . A trap occurs after installing a change file. . THESE ARE THE VALUES FROM THE TRAP PANEL: ----------------------------------------- SYS3175 A program generated an access violation at 0005f394 ANXCMSRV.EXE 0005.000f394 CS:EIP=002f:0000f394 CSLIM=0000f3ee . THESE ARE THE ENTRIES FROM THE ERROR.DAT: ----------------------------------------- ** NetView DM/2 logged at 22:35:09 19/07/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACCI6. Additional Data : 41 4e 58 41 43 43 49 36 30 30 30 34 f8 07 00 08 ANXACCI60004ø... 41 4e 58 43 53 30 44 42 41 4e 58 41 43 43 49 36 ANXCS0DBANXACCI6 41 4e 58 43 53 43 52 58 10 00 14 00 00 00 00 00 ANXCSCRX........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 07 00 00 00 00 00 00 00 00 00 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 22:35:14 19/07/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXAPCUE. Return codes were: Primary=16, Secondary=20, Auxiliary=0. Additional Data : 41 4e 58 41 50 43 55 45 30 30 30 31 41 4e 58 43 ANXAPCUE0001ANXC 53 43 52 58 44 65 6c 65 74 65 20 52 65 71 20 54 SCRXDelete Req T 61 62 6c 65 10 00 14 00 00 00 00 00 00 00 00 00 able............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 f8 07 00 08 41 4e 58 43 53 30 ......ø...ANXCS0 44 42 41 4e 58 41 43 43 49 36 00 00 00 00 00 00 DBANXACCI6...... 00 00 10 00 14 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 07 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 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: ANXCMSRV.EXE PROBLEM CONCLUSION: Corrected the management of the deletion of the INSTALL request once executed. PTRNBR: 4U00513 APARNBR: PJ21870 PTFNBR: XREFP02 EXTERNAL SYMPTOM: A TOO MANY SENDING REQUEST PENDING MESSAGE REPEATED INDEFINETLY IN THE MESSAGE.DAT PROBLEM SUMMARY : Running a batch CMD that executes more than 100 sends could generate a repeated issue of the message ANX0852, <too many send request pending>, in the message dat file. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: Corrected the process to queue SEND tasks to TC (Transmission Controller). PTRNBR: 4U00514 APARNBR: PJ21871 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DOS CC CLIENT FAILS TO EXECUTE BATCH FILES IN PRISTINE SCENARIO PROBLEM SUMMARY : The DOS CC Client fails to execute batch files, running in Pristine scenario, if the boot diskette was used before in a similar scenario. The failure occurs because COMMAND.COM file is deleted from ANXDPRST\BIN during first batch file execution. COMPONENTS CHANGED OR ENHANCED: ANXCMBOT.EXE PROBLEM CONCLUSION: Corrected the management of batch file execution. PTRNBR: 4U00516 APARNBR: PJ20900 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CDM DIALOG DOES NOT REGISTER ERROR/MESSAGE WINDOWS OPENING PROBLEM SUMMARY : . This error is present only for environments different from Focal Point. . Failing scenario: ----------------- 1. start CMD dialogs 2. from the CDM catalog screen select WINDOWS -> Local Message Log or Local Error Log. 3. the Local Message Log (or Local Error Log) window is correctly opened. 4. Now attempt to exit/close either log display using the pull down menus or F3/Alt F4 and you get a message box asking if you want to terminate NVDM/2. . The Alt F4 option should allow to close the message/error logs without terminating NVDM/2. (This is how other NVDM/2 windows work). . Reference : PMR 2E814 B072 C649 COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: For the specific environment (not Focal Point) changed the process to record opened CDM dialogs. PTRNBR: 4U00517 APARNBR: PJ21872 PTFNBR: XREFP02 EXTERNAL SYMPTOM: ACTIVATE FAILS IF INSTALL IN SERVICE AREA IS WITH /C PARAMETER PROBLEM SUMMARY : . This problem has been identified by customer Bank of Austria. . Installing a given Change File in Service Area which refers a section FileSpecList with some files with /C parameter associated, could results in a failure of the ACTIVATE in on the following condition: . 1. the Machine has the LAN server installed 2. The file installed with /C is deleted from the Active area (after the install on service). . The related message and error logs are: . MESSAGE DAT =========== ** NetView DM/2 logged at 17.02.39 08.08.1995 ** ANX0081: (E) The ACTIVATE request on workstation 'UBSM111' was unsuccessful due to errors. . ERROR DAT ========== ** NetView DM/2 logged at 17.02.02 08.08.1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXCCCOE. Return codes were: Primary=8, Secondary=0, Auxiliary=2. Additional Data : 41 4e 58 43 43 43 4f 45 30 30 30 31 41 63 63 65 ANXCCCOE0001Acce 73 73 00 00 53 65 74 49 6e 66 6f 00 00 00 00 00 ss..SetInfo..... 00 00 00 00 08 00 00 00 02 00 44 3a 5c 54 54 54 ..........D:½TTT 54 5c 43 31 56 32 5c 54 45 53 54 33 2e 44 41 54 T½C1V2½TEST3.DAT 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 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: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The parameter /C is now correctly managed by the install function. PTRNBR: 4U00518 APARNBR: PJ19981 PTFNBR: XREFP02 EXTERNAL SYMPTOM: TRAP EXECUTING A REMOTE DELETE PROBLEM SUMMARY : A remote request of DELETE for a global name causes a TRAP on the CC Server. After this TRAP took place, any attempt to restart CDM results as the same TRAP. To recover from this situation the User has to replace the current SNA files with related BAK ones. Also a local CDM DELETE request causes some error messages in the message.dat but in this case the cleanup of the .SNA files is not required. . Hereafter the TRAP information: . A program generated an access violation at 0005a305 P1=00000000 P2=ffffffff P3=xxxxxxxx P4=xxxxxxxx EAX=0000000d EBX=0000000d ECX=00000006 EDX=00000000 ESI=00000000 EDI=00000000 DS=01b7 DSACC=00f3 DSLIM=00000ff67 ES=0000 ESACC=**** ESLIM=******** FS=050b FSACC=00f2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=002f:0000a305 CSACC=00fb CSLIM=0000fc59 SS:ESP=079f:0000df0e SSACC=00f3 SSLIM=0000f9ff EBP=0000df28 FLG=00012246 . --- The messages stored in the message.dat are: . ** NetView DM/2 logged at 10:22:38 1995-08-18 ** ANX0063: (I) The file identified by Global Name '<global name>' and Local Name '<local name> has been deleted. ** NetView DM/2 logged at 10:22:38 1995-08-18 ** ANX0082: (E) A request has not been processed because the SNA/FS Server detected an error. ** NetView DM/2 logged at 10:22:55 1995-08-18 ** ANX0189: (E) System abend '2'. . The related error.log entry is: . ** NetView DM/2 logged at 10:22:38 1995-08-18 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXBIP05. Return codes were: Primary=21061, Secondary=0, Auxiliary=0. Additional Data : 41 4e 58 42 49 50 30 35 30 30 30 32 41 4e 58 42 ANXBIP050002ANXB 49 50 30 35 02 0b 00 45 52 52 5f 4f 50 5f 43 4f IP05...ERR_OP_CO 4e 54 5f 46 4c 41 47 NT_FLAG .������������������������������������������������������������������������������ NOTE: . If the DELETE is locally executed by the command CDM DELETE <global name> even if the messages ANX0063 and ANX0082 and the above error log are recorded, the DELETE request is executed and the SNA files are not corrupted so no need to replace these. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: Corrected an internal process. PTRNBR: 4U00519 APARNBR: PJ21271 PTFNBR: XREFP02 EXTERNAL SYMPTOM: MESSAGE ANX1470, 'CANNOT OPEN ANXCLCK FILE' AT CDM START PROBLEM SUMMARY : The message ANX1470, 'Cannot open ANXCLCK file', is displayed when the following conditions take place at the same time on a CC Server: . - the CDM START is issued - before the CDM START command is completed, from another OS/2 session, another CDM command is issued. . In particular, this problem occurs when a lot of local clients are defined because in this case the CDM START command takes a long time to complete. COMPONENTS CHANGED OR ENHANCED: ANXCLQ4S.DLL ANXCLQ2S.DLL PROBLEM CONCLUSION: The timeout for accessing the ANXCLCK file has been brought from 3 to 30 minutes because the CDM START command may take a long time when many clients are defined. PTRNBR: 4U00522 APARNBR: PJ21873 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DOS CC CLIENT SHOULD BE ENHANCED TO SUPPORT DRIVELETTERS KEYWORD INTO THE IBMNVDM.INI FILE PROBLEM SUMMARY : DriveLetters keyword in a OS2 CC Client allows Customer to choose letters of the drives used by redirector to attach CMREQ, SHAREA, SHAREB, FSDATA directories of the CC Server: DOS CC Client should support the same. COMPONENTS CHANGED OR ENHANCED: NVDMIDOS.EXE ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE PROBLEM CONCLUSION: DriveLetters keyword has been added as valid key of the DOS CC Client IBMNVDM2.INI file. This keyword has the same syntax of the OS/2 CC Client but it is not mandatory in the sense that if not specified the old behavior is kept (i.e. no DriveLetters keyword is added by default). PTRNBR: 4U00525 APARNBR: PJ21874 PTFNBR: XREFP02 EXTERNAL SYMPTOM: NVDMINST /CO FAILS DUE TO MISSING *.BND AFTER HAVING REINSTALLED THE PRODUCT FROM PRODUCT IMAGES PROBLEM SUMMARY : Running NVDMINST /CO later an unattended installation results as a failure with message ANX8296 (E) (SQL 1004, incorrect environment). COMPONENTS CHANGED OR ENHANCED: ANXTAB_F.LST ANXTAB_N.LST ANXTAB_X.LST PROBLEM CONCLUSION: The failure is due to duplicate rows into the installation list concerning some BIND files. This inconsistency causes the installation program to process twice some statements resulting as some BIND files to be deleted. Corrected. PTRNBR: 4U00526 APARNBR: PJ20512 PTFNBR: XREFP02 EXTERNAL SYMPTOM: LIMITATION IN NUMBER OF NAMES TO BE PACKED BY BUILD FUNCTION PROBLEM SUMMARY : Issuing a CDM BUILD with (*.* /IS), from a source directory (/S parameter) with 50 subdirs where each of these subdirs contains other 20 subirs containing 10 files (total number of files showed by dir /S = 13152), results as : SYS 1811 TRAP (D) COMPONENTS CHANGED OR ENHANCED: ANX.MSG CDM.EXE ANXEFAPI.DLL ANXCKPUQ.DLL PROBLEM CONCLUSION: The maximum number of names of files and directories that can be managed by the Build function is 10000. The fix avoid the trap occurrence and a proper message is displayed when this limit is reached. The new message is: ANX0312: Build failed. Too many files to be packed. PTRNBR: 4U00527 APARNBR: PJ20451 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DIR. ANX LEFT LATER AN UNATTENDED CC CLIENT INST. PROBLEM SUMMARY : Unattended NetView DM/2 CC Client installation, by changing boot drive, results as working directory ANX (needed to place DLL's to move NvDM/2 locked files at IPL) not deleted and its references on LIBPATH statement left into the CONFIG.SYS once IPLed at the end of product installation. . References: APAR PJ20451 PMR 4381E B483 C000, customer Dean Witter related COMPONENTS CHANGED OR ENHANCED: BODY.EXE PROBLEM CONCLUSION: Corrected the process to clean up working modules/DLL's used at IPL time to move NetView DM/2 modules found locked at product installation time. PTRNBR: 4U00528 APARNBR: PJ21875 PTFNBR: XREFP02 EXTERNAL SYMPTOM: AN FST FILE BELONGING TO NO ACTIVE TRANSMISSION IS FOUND IN THE FSDATA SUBDIRECTORY PROBLEM SUMMARY : If during a transmission the target machine is powered off, at the next power on, in the FSDATA remains the temporary FST file of the previous transmission. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL ANXEFAPI.DLL PROBLEM CONCLUSION: The solution was to distinguish when the transmission stopped because of a CDM STOP from when it stopped for a power off. In case it was stopped because of a power off since it is not possible to guarantee the restartability the previous FST is deleted and the checkpoint file NVDM2CKS is reorganized. PTRNBR: 4U00529 APARNBR: PJ21876 PTFNBR: XREFP02 EXTERNAL SYMPTOM: SENSE CODE 100B 000C DETECTED FROM NVDM/6000 WHEN RETRIEVING A RESOURCE. PROBLEM SUMMARY : The NetView DM/6000 receives a sense code 100B 000C when retrieving a resource from NetView DM/2 V2.1 COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem, now corrected, was due to the encoding process of the retrieve request. PTRNBR: 4U00531 APARNBR: PJ20562 PTFNBR: XREFP02 EXTERNAL SYMPTOM: UNABLE TO ALLOCATE VIRTUAL ADDRESS SPACE PROBLEM SUMMARY : . When trying to start the pm interface (CDMD) the following error is displayed: . ------------------------------------------- | Error| | | Unable to allocate virtual address | | space. 1 104857600 | | | | <ENTER> | ------------------------------------------- . References: PMR 1E026 B077 C649 PMR 7977X B160 C846. COMPONENTS CHANGED OR ENHANCED: VPMVM20.DLL PROBLEM CONCLUSION: The amount of virtual memory that the CDM dialogs requires to allocate, clashes with that available in the system. With the new VPMVM20.DLL (provided by Digitalk) it is possible to set how much virtual memory you want to reserve for the CDM Dialogs: it is done by setting an environment variable from the OS/2 window, and the argument is expressed in megabytes. The Customer can set the environment variable SMALLTALKVIRTUALALLOC either is its CONFIG.SYS or in the OS/2 session from which the CDMD is invoked. . Example of setting: . SET SMALLTALKVIRTUALALLOC=16 This setting will define 16 MB of virtual memory to reserve for CDM Dialogs. . PTRNBR: 4U00532 APARNBR: PJ20590 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CDM DIALOGS FAILS TO RETRIEVE MESSAGE/ERROR DAT FILES PROBLEM SUMMARY : This problem is present when the following conditions occur at the same time: 1) in the IBMNVDM2.INI file MESSAGE.DAT and/or ERROR.DAT files are defined under the root 2) the <START CDMD> command is issued from a directory different from that one under which the MESSAGE.DAT and ERROR.DAT are defined in the IBMNVDM2.INI file. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Corrected the process to determine the current defined paths for MESSAGE and ERROR dat files. PTRNBR: 4U00534 APARNBR: PJ20658 PTFNBR: XREFP02 EXTERNAL SYMPTOM: ANXIDISP FOR Q3 INITIATE AND INSTALL DOES NOT WORK PROBLEM SUMMARY : . Reference: PMR 5142E, customer ANZ related. . According with what stated at page 196 of the CDM Installation Guide ss19-6915-04, in the Q3 environment the default for the DISPOSITION parameter for the INSTALL and INITIATE function should be DELETE, and the default value can be changed in KEEP by setting in the config.sys the environment variable ANXIDISP=KEEP. This does not work and the default disposition is always set to KEEP. This causes the CM objects are not deleted after an INSTALL or an INITIATE function. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE README.TXT PROBLEM CONCLUSION: The correct default for disposition is KEEP because of Client/Server design. Customer that have configured as Host attached workstation (Q3 environment) their NetView DM/2 V2.1 installation and do not want to keep the change file can set the ANXIDISP to DELETE in their CONFIG.SYS to change product behavior. The NetView DM/2 V2.1 Installation & Customization guide will be amended via README.TXT . PTRNBR: 4U00535 APARNBR: PJ20751 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CDM DIALOG PERFORMANCE DECREASES WHEN PERFORMING INSTALL OR INITIATE TASKS OF SEVERAL OBJECTS PROBLEM SUMMARY : A performance problem was found when retrieving the list of clients in the 'Install' and 'Force Install' dialog, when more than one object were selected in the CDM Catalog window. Same problem also for the 'Initiate' dialog. This problem occurs only in a Server environment. . Reference: PMR 9478X B044 C866. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The list of clients is now retrieved without getting the status for each client. PTRNBR: 4U00536 APARNBR: PJ20741 PTFNBR: XREFP02 EXTERNAL SYMPTOM: CHANGE CONTROLLER ENDS BECAUSE OF ERRORS PROBLEM SUMMARY : . Reference: PMR 6277X B370 C000 . Change Controller goes down due to a synchronization problem between 2 NvDM/2 processes: DELETE_WS and CM_REQUEST when there is a large amount of defined CC Clients. The problem occurs when a CDM DELETE_WS command was issued, but all of the CM requests or task for that CC Client workstation had not yet completed on the CC Server in terms of successful acknowledge- ment (CMFxxxxx.END signal) received from CC Clients. The following entries are seen in Error.Dat: ** NetView DM/2 logged at 02:44:21 (PM) 10-13-1995 ** 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 46 69 6c 65 ANXACCSH0001File 4d 6f 76 65 44 6f 73 46 69 6e 64 00 00 00 00 00 MoveDosFind..... 00 00 00 00 14 00 00 00 03 00 44 3a 5c 49 42 4d ..........D:½IBM 4e 56 44 4d 32 5c 43 4d 52 45 51 5c 41 30 31 30 NVDM2½CMREQ½A010 38 34 33 5c 43 4d 46 2a 2e 45 4e 44 00 00 00 00 843½CMF*.END.... COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The process to verify signal from CC Client changed to prevent CC Server to end because of errors when it does not find anymore the CC Client subdirectory expected to have a signal for the CC Server. PTRNBR: 4U00538 APARNBR: PJ20793 PTFNBR: XREFP02 EXTERNAL SYMPTOM: THE LENGTH RECORD OF A RESOURCE AT HOST IS INCORRECT PROBLEM SUMMARY : Wrong record length sent to host along with an object. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: Corrected the function to calculate the record length to transmit to host along with the object. PTRNBR: 4U00539 APARNBR: PJ20829 PTFNBR: XREFP02 EXTERNAL SYMPTOM: RETURN CODE = 0 PERFORMING CDM SEND WITH INVALID PARAMETER PROBLEM SUMMARY : When using a REXX CMD file to execute a CDM SEND, if an invalid parameter is used with the command, the return code is RC=0. It should not. (It should be 5) . Reference: PMR A0292 BM18 C649 COMPONENTS CHANGED OR ENHANCED: CDM.EXE PROBLEM CONCLUSION: Line Parser module has been modified in order to issue a consistent return code. PTRNBR: 4U00540 APARNBR: PJ20980 PTFNBR: XREFP02 EXTERNAL SYMPTOM: ANX1007 MESSAGE IS INCORRECTLY ISSUED DURING THE CDM BUILD COMMAND PROBLEM SUMMARY : The CDM BUILD ends with ANX1007 message error although the maintenance level is correctly defined in the change file profile. Example: for a global name with maintenance level value=33000 this message error is displayed. . Reference: 9340X B200 C838 COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: The semantic check performed to control the correctness of the tokens in the global name was updated in order to manage maintenance level also greater than 32767. PTRNBR: 4U00541 APARNBR: PJ21269 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DEFER POPUP NOT DISPLAYED BY ACTIVATE WITH FORCE=NO PROBLEM SUMMARY : Issuing an Activate with FORCE = NO, sometimes the popup panel asking if the Activate has to be deferred or not, is not displayed and the Activate immediately starts. In particular, this problem has been experienced by Customers after to have issued an INITIATE function before the Activate. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The problem, now corrected, was due to a wrong variable declaration and initialization. The wrong value of this variable caused the POP-UP panel not to be displayed. PTRNBR: 4u00542 APARNBR: PJ21119 PTFNBR: XREFP02 EXTERNAL SYMPTOM: BAD UPDATE OF IBMNVDM2.ALS DURING REMOVE FUNCTION PROBLEM SUMMARY : After to have installed in Service area an object created with the /IS option in the FileSpecList of the Build profile, and after to have removed it by the remove function, the files and directories are correctly deleted from the Service Area but the statements of the involved directories are not eliminated from the file IBMNVDM2.ALS (Activation list file). This causes that, when an Activate function is executed it fails with the message: ================================================================ ANX0081: (E)ACTIVATE request on workstation 'LT0361A0' was unsuccessful due to errors. ================================================================ And with the following error.log in the error.dat file: ================================================================ ** NetView DM/2 logged at 02:49:04 (PM) 13-11-1995 ** 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: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: Corrected the management of the IBMNVDM2.ALS list. PTRNBR: 4U00543 APARNBR: PJ21476 PTFNBR: XREFP02 EXTERNAL SYMPTOM: THE NVDMLZW DECOMPRESSION OF A PARTICULAR RESOURCE FAILS PROBLEM SUMMARY : Sending a compressed object, from host to node, results as a decompression failure of the object with message ANX0170. The sense code reported to host is: 100b 000c COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem, now corrected, was raised by the size of the object that created a management problem of the TC (transmission Controller) buffers. PTRNBR: 4U00545 APARNBR: PJ21877 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DOS CC CLIENT FAILS TO BUILD MINIMAL CONFIGURATION FILES IF ANY STATEMENT OF THE ACTIVE ONES IS GREATER THAN 128 CHARACTERS. PROBLEM SUMMARY : NetView DM/2 does not complete the build of minimal configuration files when a statement greater than 128 characters is found in the active ones. The message ANX1803 is shown that states a too long line has been found. Since DOS cut any line exceeding the 128 byte length, this error can become a warning. In other words since this statement is already in configuration files and it does not cause any problem, it can be inserted in minimal configuration files too. . Reference: PMR 4694X B033 C000 COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.EXE PROBLEM CONCLUSION: Corrected the management of the message from error to warning in order to prevent the process to abort when processing a line greater than 128 characters. PTRNBR: 4U00546 APARNBR: PJ21577 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DOS CC CLIENT AGENT ENDS DUE TO MEMORY LACK WITHOUT SHOVING MEANINGFUL MESSAGE TO IDENTIFY THE PROBLEM SOURCE PROBLEM SUMMARY : In case of a memory lack, the DOS CC Client fails without logging meaningful message to identify the source of the failure. . It only logs the following error into the ERROR dat file: . Error detected in NetView DM/2 CM component. The error was generated in module ANXCRPH0. Return codes were: Primary=16, Secondary=20, Auxiliary=31. Additional Data : 41 4e 58 43 52 50 48 30 30 30 30 31 41 4e 58 43 ANXCRPH00001ANXC 43 50 4d 4d 44 6f 73 47 65 74 4d 65 73 73 61 67 CPMMDosGetMessag 65 e COMPONENTS CHANGED OR ENHANCED: ANXCMCL1.EXE ANXCMCL2.EXE ANXCMCL3.EXE ANXCMPMC.EXE PROBLEM CONCLUSION: Since the lack of memory prevents the DOS CC Client to retrieve and to issue any message, the only way to add more information about the source of the problem was reached in adding a line, advising a lack of memory, to the error log generated when the failing event takes place. PTRNBR: 4U00547 APARNBR: PJ21878 PTFNBR: XREFP02 EXTERNAL SYMPTOM: REQUIREMENT TO UPDATE RULE FILE .BKC TO REFER IBM DOS V7 PROBLEM SUMMARY : Backup file .bkc should be update in order to consider IBM DOS V7 in the list of DOS to which any rule can be applied. . Reference: PMR 2506X B033 C000 COMPONENTS CHANGED OR ENHANCED: ANXIDMCF.BKC PROBLEM CONCLUSION: The .BKC file enhanced to refer IBM DOS V7. PTRNBR: 4U00548 APARNBR: PJ21272 PTFNBR: XREFP02 EXTERNAL SYMPTOM: TRAP IN ANXBASE.DLL ISSUING CDM START OPERATION PROBLEM SUMMARY : A trap may occur issuing a CDM START command, the trap registers are: =========================================================== SYS3175 A program generated an access violation at 11929e86 ANXBASE.DLL 000a:11906836 P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000000 ESI=00002555 EDI=00000529 DS=8c4f DSACC=00f3 DSLIM=000054f3 ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=8c97:00009e86 CSACC=00fb CSLIM=0000dc8e SS:EIP=7ecf:00009bba SSACC=00f3 SSLIM=0000bfff EBP=00009cce FLG=00012282 =========================================================== COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL PROBLEM CONCLUSION: Corrected internal management of a string. PTRNBR: 4U00550 APARNBR: PJ21350 PTFNBR: XREFP02 EXTERNAL SYMPTOM: BOOT DISKETTE CRETED WITH MS DOS ARE NOT RECOGNIZED BY NVDMBDSK PROBLEM SUMMARY : In order to create a Pristine Boot Diskette to run a pristine scenario to install a DOS CC Client machine, a DOS bootable diskette need to be customized, to include NetView DM/2 code, by NVDMBDSK utility. This utility, unfortunately, does not recognize as valid diskette, one built with MS DOS via format /S. . Reference: PMR 4x768 B082 C649 COMPONENTS CHANGED OR ENHANCED: NVDMBDSK.EXE PROBLEM CONCLUSION: In order to understand if the diskette is able to boot, NVDMBDSK checks if system files are there. Before this fix, the check was only performed against IBM PC DOS system files. Now, the check is done also for MS DOS system files allowing NVDMBDSK utility to recognize as valid MS DOS bootable diskette. PTRNBR: 4U00552 APARNBR: PJ21471 PTFNBR: XREFP02 EXTERNAL SYMPTOM: EMPTY DIRECTORIES DELETED BY REMOVE OF SERVICE AREA PROBLEM SUMMARY : Assuming to install two objects in Service area as 'removable', where the first object contains also empty directories, and then remove the second object. The remove of the second object causes the deletion of all the empty directories of the first one in the Service area while the .ALS file is correctly updated (i.e. only the second object statements are deleted). The mismatch between the .ALS (correct) information and the Service area (wrong) information causes at the Activate time the error identified by the following entry in the error.dat file: **************************************************************** 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 ...... ---------------------------------------------------------------- Also, the message ANX0081 (Activate failure) is logged. COMPONENTS CHANGED OR ENHANCED: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The empty directories are not deleted anymore from the service area. PTRNBR: 4U00553 APARNBR: PJ21879 PTFNBR: XREFP02 EXTERNAL SYMPTOM: NVDMUPO DOES NOT REPLACE ALL OCCURRENCES OF TARGETDIR MACRO PROBLEM SUMMARY : . References: Appends to NETVDM2 forum by both Charlie Brown and Alessio Frenquelli. . The NVDMUPO utility does not replace any $TargetDir macro in a MOD file but just the first occurrence. The scenario to verify this event is hereafter described. 1 - Create a MOD file such follows: îSTARTUP.CMD® AddStatement(Bottom,<$(TargetDir)\fred.exe P1 P2 P3>) AddStatement(Bottom,<$(TargetDir)\fred.exe $(TargetDir) P2 P3>) AddStatement(Bottom,<$(TargetDir)\fred.exe $(TargetDir) > $(TargetDir) P>) 2 - Invoke the following command: NVDMUPO NVDMUPO.MOD /T:h:\fred' 3 - Observe that NVDMUPO has updated the STARTUP.CMD as follows: h:\fred\fred.exe P1 P2 P3 h:\fred\fred.exe $(TargetDir) P2 P3 h:\fred\fred.exe $(TargetDir) $(TargetDir) P3 COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE PROBLEM CONCLUSION: Corrected the process to resolve $TagertDir variable occurrences referred into a MOD file. Now, more occurrences of $TargetDir could be specified in a statement of a given MOD file. PTRNBR: 4U00555 APARNBR: PJ21642 PTFNBR: XREFP02 EXTERNAL SYMPTOM: WRONG OPTION REFERENCES FOR SEND SWITCH IN INITIATE/INSTALL PROBLEM SUMMARY : The NetView DM/2 Change Distribution Manager User's Guide Version 2.1 states that the CDM INSTALL and INITIATE commands support the following options when using the /SEND parameter: - /ASIS - /REPL - /PROC . (Reference: CDM INSTALL/INITIATE syntax command) . This is not correct: the CDM INSTALL or CDM INITIATE may be issued with the /SEND parameter but without any option associated. When installing an object with the /SEND parameter, the file is sent as is and replaced with the same global name, by default. COMPONENTS CHANGED OR ENHANCED: README.TXT CDM.INF PROBLEM CONCLUSION: The NetView DM/2 V2.1 CDM User's Guide has been amended via README.TXT . PTRNBR: 4U00556 APARNBR: PJ21812 PTFNBR: XREFP02 EXTERNAL SYMPTOM: RUNTIME ERROR IN 'OPEN WORKSTATION' DIALOG, 'OBJECTS...' FUNCTION PROBLEM SUMMARY : . Assuming the following scenario working with CDM dialogs: . a - Open CC Domain window b - Select/Open a workstation c - From 'Open workstation' dialog select 'Objects...' function . The above sequence of tasks could result (random) with the issue of the following message: . <Runtime Error: System Primitive failed> COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: The error, now corrected, was due to an invalid check retrieving the 'Date and time' to be displayed in the 'Installed objects at <wsname>' dialog. PTRNBR: 4U00557 APARNBR: PJ21270 PTFNBR: XREFP02 EXTERNAL SYMPTOM: REQUIREMENT TO SUPPORT GREEK CODEPAGES AND COUNTRY CODE PROBLEM SUMMARY : This PTR has been opened to manage a requirement from Greece to enhance NetView DM/2 V2.1 to support either Greek country code (030) and Greek codepages (869, 813). COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL ANXBFTH.DLL ANXEFAPI.DLL ANXBASE.DLL PROBLEM CONCLUSION: The NetView DM/2 V2.1, with this change, now supports country code 030 and codepages 869/813. PTRNBR: 4U00558 APARNBR: PJ21881 PTFNBR: XREFP02 EXTERNAL SYMPTOM: EXCESSIVE ERROR.DAT GROWS DUE TO REPEATED ANXACCDO MESSAGES PROBLEM SUMMARY : Randomly, when an error occurs interfacing NetBIOS, the ANXACCDO module seems to loop a cycle in which a message is recorded in ERROR.DAT several times. In some cases this cycle is so long that seems to be infinite and the ERROR.DAT grows so much. Hereafter some examples of the repeated logs in the ERROR.DAT file. . EXAMPLE 1 ========= ** NetView DM/2 logged at 11:43:01 29/11/1995 ** 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.... 13 00 30 30 4e 45 54 42 49 4f 53 ..00NETBIOS . EXAMPLE 2 ========= . ** NetView DM/2 logged at 11:43:01 29/11/1995 ** 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.... 3b 00 30 30 4e 45 54 42 49 4f 53 ..00NETBIOS COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: Corrected the process that manages the signalling between CC Server and CC Client, and viceversa, in case a NetBIOS error takes place. PTRNBR: 4U00559 APARNBR: PJ21305 PTFNBR: XREFP02 EXTERNAL SYMPTOM: HELP FOR MESSAGE ANX1773 SHOULD BE CHANGED PROBLEM SUMMARY : The help for message ANX1773 refers always module CMLOADER.COM to indicate the DOS CC Client TSR. It should be changed to refer the correct module name for TSR that is ANXCMLDR.COM COMPONENTS CHANGED OR ENHANCED: ANXH.MSG PROBLEM CONCLUSION: Explanation related to message ANX1773 has been corrected. PTRNBR: 4U00560 APARNBR: PJ21882 PTFNBR: XREFP02 EXTERNAL SYMPTOM: REQUIREMENT TO CUSTOMIZE MAXIMUM LOG FILE SIZES PROBLEM SUMMARY : . The Customers have placed a requirement to allow the customization of the maximum size for MESSAGE.DAT and ERROR.DAT files. . COMPONENTS CHANGED OR ENHANCED: ANXBASE.DLL ANX.MSG README.TXT PROBLEM CONCLUSION: . Two new environment variables were introduced, to customize both MESSAGE and ERROR dat maximum log sizes, such as: . SET ANXMSGSZ=<number> SET ANXERRSZ=<number> . The <number> value is the desired size for MESSAGE.DAT and ERROR.DAT expressed in Kbytes. . After to have set these variables, when a new entry is to be added to these files, if the filesize exceeds the specified value, the file is saved in a backup file with the same name and extension ANX, a new file is created and the new entry stored at the beginning of this file. . We recommend to set these variables to 1024 (1Mbyte) so that the information stored in .ANX file is enough for the analysis in case of problems. PTRNBR: 4U00561 APARNBR: PJ21719 PTFNBR: XREFP02 EXTERNAL SYMPTOM: DECOMPRESSION FAILURE OF A FILE COMPRESSED WITH PKZIP PROBLEM SUMMARY : The scenario is the following: A file, compressed with pkzip, is cataloged at the node with /TC:NVDMLZW and is sent to host with the /COMP option. The global name is stored at host side like compressed by NVDMLZW. When it is resent to the same node or to another one the ANX0170 message 'decompression failure' is logged and the appropriate sense code is returned to host. Anyway the file is intact, so it is possible to pkunzip it normally. COMPONENTS CHANGED OR ENHANCED: ANXBFTH.DLL PROBLEM CONCLUSION: The problem is due to the fact that the nvdmlzw algorithm is not efficient on a file already zipped as well as it is not efficient to compress twice a file (on the second time, the size in bytes is greater than the first time). In this situation the specific server didn't compress the file (because of no efficiency) but sent to host the name of the compression algorithm and a compressed status equal to 1. So, the file was stored like compressed but really it was not. Sending it again to the server the node tried to decompress it but the decompression algorithm fails since the file was really not compressed. In such a situation, now with this fix, the compressed status sent is 2 (not compressed) while the compression algorithm name is blank. PTRNBR: 4U00562 APARNBR: PJ21711 PTFNBR: XREFP02 EXTERNAL SYMPTOM: SPECIFY THAT NODE TYPE OS/2 IS VALID ALSO FOR AIX PROBLEM SUMMARY : Need to mention in documentation referencing the ADD_DEST command (and anywhere else NVDM2 affinity with multiple operating systems is discussed) that AIX is similar to OS2 with respect to functional interaction. Ref PMR 1X682,033. COMPONENTS CHANGED OR ENHANCED: README.TXT PROBLEM CONCLUSION: Amended NetView DM/2 V2.1 User's Guide via README.TXT PTRNBR: 4U00406 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: ERROR WHEN RESTARTING CDM. THE CHANGE CONTROLLER ENDS WITH THE MESSAGE ANX0074. PROBLEM SUMMARY : When the product is stopped meanwhile it is creating the Function File for some clients workstations, the next restart results as Change Controller ended with errors. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The problem was due to the restart mechanism, now corrected. PTRNBR: 4U00407 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: RECEIVER EXCEPTION FOR 0 BYTES LONG FILES PROBLEM SUMMARY : When 0 bytes long files are being received from a NetView DM/MVS R1.5, the Specific Server component of the NetView DM/2 logs 085A SNA sense data (exception). COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: Now it is possible to send and to receive empty resource because a check about the presence of 153f structure (that is part of the 1541 one) is done. PTRNBR: 4U00412 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: WINOS2 DOES NOT START BECAUSE OF INCORRECT SYSTEM.INI CREATED BY NVDMUPO PROBLEM SUMMARY : Running NVDMUPO to update *.INI, according to a modification file generated by monitoring a Windows based application installation under WINOS2, results as incorrect SYSTEM.INI because of copied from PROGRAM.INI . COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE PROBLEM CONCLUSION: Corrected internal process. PTRNBR: 4U00418 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: THE CHANGE CONTYROLLER GOES DOWN WITH ANX0211 MESSAGE. PROBLEM SUMMARY : Assume the following scenario: . -Deleting an object that at the CC Server has some CM entry for some workstations. . -The delete successful complete, but the message ANX0172 is logged. In fact, the Delete, when the object involved in the request as CM entry for some workstation, will cancel ONLY the local name but not the Global Name in the catalog. . -At this point trying to install this object on a Client. . This last action results as Change Controller to fail with message ANX0211. COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE PROBLEM CONCLUSION: The Change Controller went down because it called the Pack/Unpack routine passing a blank local file name. Now, the Change Controller validates the GLOBAL NAME to install as linked to an existing local file before to invoke Pack/Unpack internal routine and will issue a consistent message if no local file name is found. PTRNBR: 4U00419 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: NVDMUPO.LOG NOT CREATED UNDER <PRODUCT_ROOT>\BIN PROBLEM SUMMARY : When running NVDMPRE or NVDMPOST, the related NVDMUPO.LOG is not created or updated under the <product_root>\BIN path as expected. COMPONENTS CHANGED OR ENHANCED: NVDMPRE.EXE NVDMPOST.EXE PROBLEM CONCLUSION: NVDMUPO.LOG file is now created under the <product_root>\BIN directory. PTRNBR: 4U00434 APARNBR: PJ19582 PTFNBR: NVDM2FP1 EXTERNAL SYMPTOM: CDM DIALOG, WHEN OPENING CC DOMAIN WINDOW, COULD OCCUR THAT SELECTED MENU HAS ENABLED ALL THE FUNCTIONS ALTHOUGH NO ITEM SELECTED PROBLEM SUMMARY : Assume to open CC Domain window. Clicking on 'Selected' menu, the related functions are enabled although no items are selected in the list. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Changed Dialog internal process. PTRNBR: 4U00439 APARNBR: PJ19582 PTFNBR: NVDM2FP1 EXTERNAL SYMPTOM: CDM DIALOG RUNTIME ERROR WHILE DELETING A REQUEST PROBLEM SUMMARY : Runtime error occurs on CDM Dialog when trying to delete a request in 'In progress' status. This error doesn't occur systematically. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Changed Dialog internal process. PTRNBR: 4U00440 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: RESTART IS NOT POSSIBLE IF CDM IS STOPPED AT TARGET PROBLEM SUMMARY : If a transmission is interrupted by a CDM STOP at the target, the transmission doesn't restart where it had left but from the very beginning. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL PROBLEM CONCLUSION: The problem was that the start had the effect to reorganize the checkpoint file NVDM2CKS deleting all the information about the number of bytes received when the stop was performed. PTRNBR: 4U00466 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: PERFORMANCES, CDM LIST /WS TAKES TOO MUCH TIME PROBLEM SUMMARY : Response time of commands such as: CDM LIST /WS and CDM LIST_IT /WS are sensibly increased from 2.0 to 2.1. . Moreover, when the number of local clients is greater than 255, there is a TRAP D when issuing the command: CDM LIST_IT <group name> /WS COMPONENTS CHANGED OR ENHANCED: CDM.EXE ANXEFAPI.DLL PROBLEM CONCLUSION: The performances of version 2.1 are back to those of version 2.0. PTRNBR: 4U00468 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: OS2CAMERA FAILS TO MONITOR OVER HPFS386 PROBLEM SUMMARY : The Disk Camera considers to include the whole directory, when just a file is added to it, monitoring disk activities over HPFS386 filesystem. COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE PROBLEM CONCLUSION: The Disk Camera failed to monitor over HPFS386 file system because of directory timestamp is updated even if just a file is added. Even if this is a not correct behavior of the file system, the Disk Camera was enhanced to prevent mis monitoring. PTRNBR: 4U00469 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: FAILING ACTIVATE WITH LAN SERVER AND EMPTY *.ALS FILE. Reference: PMR 5137X B200 C838 PROBLEM SUMMARY : Issuing an Activate on a machine with Lan Server installed and with an empty activation list file (no files to be moved), after the reboot the activate ends with the message ANX0081 (Activate unsuccessfull) and the following error.log is logged in the ERROR.DAT : ** NetView DM/2 logged at 13:23:11 11/05/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXCCCOE. Return codes were: Primary=8, Secondary=0, Auxiliary=110. Additional Data : 41 4e 58 43 43 43 4f 45 30 30 30 31 43 5f 46 75 ANXCCCOE0001C_Fu 6e 63 00 00 66 6f 70 65 6e 00 00 00 00 00 00 00 nc..fopen....... 00 00 00 00 08 00 00 00 6e 00 43 3a 5c 49 42 4d ........n.C:½IBM 4e 56 44 4d 32 5c 42 49 4e 5c 49 42 4d 4e 56 44 NVDM2½BIN½IBMNVD 4d 32 2e 44 41 43 00 00 00 00 00 00 00 00 00 00 M2.DAC.......... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ............... ............... ............... ............... 00 00 00 00 00 00 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: ANXCMCLS.EXE ANXCMCLC.EXE PROBLEM CONCLUSION: The problem was due to the fact that when an empty Activation List was detected, the IBMNVDM2.DAC creation statements are not executed even if the Lan Server is installed. So when NetView DM/2 looked for this file, after the reboot, it failed. The problem is now solved by creating the IBMNVDM2.DAC file also when the activation list is empty. PTRNBR: 4U00471 APARNBR: PJ19582 PTFNBR: XREFP01 EXTERNAL SYMPTOM: AFTER ATTRIBUTE DOES NOT WORK WITH BLANKS PROBLEM SUMMARY : AFTER:<my app> does not work because of blanks. COMPONENTS CHANGED OR ENHANCED: NVDMUPO.EXE PROBLEM CONCLUSION: Corrected the attribute parsing process. PTRNBR: 4U00474 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: MIGRATION NOT ALLOWED FROM NvDM/2 V2.0 STANDALONE LAN TO NvDM/2 V2.1 INTERCONNECTED LANs PROBLEM SUMMARY : Trying to install NetView DM/2 V2.1 on top an existing NetView DM/2 V2.0, configured as standalone LAN, the product installation program failed because of MIGRATION NOT ALLOWED. COMPONENTS CHANGED OR ENHANCED: BODY.EXE PROBLEM CONCLUSION: The migration is now allowed. PTRNBR: 4U00477 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: UNATTENDED INSTALLATION FAILS ON MACHINE HAVING FIXED DISK FORMATTED AS FAT FILESYSTEM PROBLEM SUMMARY : Reference : PMR 5X375 B395 C000 . Customer is receiving a SYS1718 error, the system cannot find the file 'ANXACTVD', when booting the system. COMPONENTS CHANGED OR ENHANCED: BODY.EXE PROBLEM CONCLUSION: Corrected handling of the NvDM/2 V2.1 related statements into CONFIG.SYS file. PTRNBR: 4U00478 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: RETRIABILITY WHEN ALLOCATE FAILS WITH A NORETRY SENSE CODE PROBLEM SUMMARY : A customer required to make retriable a no-retriable sense code returned by an APPC allocate verb. COMPONENTS CHANGED OR ENHANCED: ANXSNADS.EXE PROBLEM CONCLUSION: The no-retriable situations after an allocate were changed in retriable situations every 10 minutes. PTRNBR: 4U00479 APARNBR: PJ19581 PTFNBR: XREFP01 EXTERNAL SYMPTOM: ANXADM UTILITY SOMETIMES COULD ABNORMALLY END (TRAP) PROBLEM SUMMARY : Invoking ANXADM utility could result as an abnormal end (TRAP) over some machine. COMPONENTS CHANGED OR ENHANCED: ANXADM.EXE PROBLEM CONCLUSION: Solved using a different include file when building the code. PTRNBR: 4U00482 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: a - NVDMLZW OPERATIONs PRODUCES 100B0001 b - SCB RESOURCE SEND FROM THE HOST WITH THE PRIME CHAR '40'X WILL BE DECOMPRESSED AT THE NODE WITH '00'X INSTEAD OF '20'X AS PRIME CHAR. PROBLEM SUMMARY : The former problem occurs when the User performs a RETRIEVE from the Host specifying that the resource must be compressed. . At the node the algorithm used as default in the INI file is NVDMLZW. . In this case the node issues 100b0001 when trying to encode the request to sent to the host. . The problem also occurs if the User send to the Host a resource specifying the NVDMLZW as algorithm. . In this case no sense code are sent to the host but the send fails with ANX0698: sense code 085a0000. . The latter problem is that when a resource is sent from the Host as compressed with SCB algorithm and prime char of '40'x as default at the node the resource is decompressed with '00'x as prime char instead of '20'x. COMPONENTS CHANGED OR ENHANCED: ANXLBFS.DLL. PROBLEM CONCLUSION: The problem was due to an incorrect management of the NVDMLZW algorithm and SCB prime character, now fixed. PTRNBR: 4U00484 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: ATTENDED MIGRATION FROM A STANDALONE CC SERVER 2.0 TO 2.1 FAILS PROBLEM SUMMARY : After migrating a Standalone CC Server from NvDM/2 2.0 XR20354 to NvDM/2 2.1 XR20466 the Change Controller ends because of errors and the object installed remains in status SCHEDULED. . Hereafter the Message and Error Dat that refer to the problem and the CMF0000x.ERR file created under CMREQ directory: . MESSAGE DAT ----------- . ** NetView DM/2 logged at 17:40:21 16/06/1995 ** ANX1315: (I) Invoking External Program: 'D:½SHAREA½IMG½NVDM466½NVDMINST.EXE With Parms: '/CDM:C /LDU /R:D:½SHAREA½RSP½NVDM2½NVDMQ2.RSP /T:C:½IBMNVDM2 /S:D:½SHAREA½IMG½NVDM466 /L:D:½SHAREB½LOG½NVDM2½LT0017A0.LOG' . ** NetView DM/2 logged at 17:50:25 16/06/1995 ** ANX1337: (I) The CDM Agent is ready to process requests. . ** NetView DM/2 logged at 17:50:28 16/06/1995 ** ANX0197: (I) The External Install Program 'D:½SHAREA½IMG½NVDM466½NVDMINST.EXE terminated successfully with the warning exit code 'fe04'. . ** NetView DM/2 logged at 17:50:34 16/06/1995 ** ANX0051: (I) The CDM Change Controller is ready to process requests. . ** NetView DM/2 logged at 17:51:09 16/06/1995 ** ANX0162: (I) User parameters successfully loaded by redirector from IBMNVDM2.INI file. . ** NetView DM/2 logged at 17:51:31 16/06/1995 ** ANX0074: (E) The Change Controller ended because of errors. . ERRORE DAT ---------- . ** NetView DM/2 logged at 17:51:24 16/06/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPMM. Additional Data : 41 4e 58 41 43 50 4d 4d 30 30 30 34 f8 07 00 08 ANXACPMM0004Ž... 41 4e 58 43 53 30 44 42 41 4e 58 41 43 50 4d 4d ANXCS0DBANXACPMM 41 4e 58 43 53 43 52 58 10 00 04 00 00 00 00 00 ANXCSCRX........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 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 00 00 ................ . ** NetView DM/2 logged at 17:51:24 16/06/1995 ** Error detected in NetView DM/2 CM component. The error was generated in module ANXACPMM. Additional Data : 41 4e 58 41 43 50 4d 4d 30 30 30 34 f8 07 00 08 ANXACPMM0004Ž... 41 4e 58 43 53 30 44 42 41 4e 58 41 43 50 4d 4d ANXCS0DBANXACPMM 41 4e 58 43 53 43 52 58 10 00 04 00 00 00 00 00 ANXCSCRX........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 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 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ . ** NetView DM/2 logged at 17:51:25 16/06/1995 ** 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.... 3b 00 30 30 4e 45 54 42 49 4f 53 ;.00NETBIOS COMPONENTS CHANGED OR ENHANCED: ANXCMSRV.EXE. PROBLEM CONCLUSION: The problem was due to a empty field, retrieved from CM Function File (i.e. CMFxxxxx), that was padded with zeros when migrating the database. Now, in case of this field results as empty, this is set to $SERVERGN. PTRNBR: 4U00485 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: CDM BUILD RESULTS AS ABNORMAL END (TRAP) WHEN FILESPECLIST GREATER THAN 64KB PROBLEM SUMMARY : When a CDM BUILD command is issued and the change file profile contains a filespeclist greater than 64KB an abnormal end (TRAP) occurs. COMPONENTS CHANGED OR ENHANCED: ANXEFAPI.DLL PROBLEM CONCLUSION: Now, when the 64KB limit is reached, an error message is displayed (ANX0181E). PTRNBR: 4U00489 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: RUNTIME ERROR IN CDM DIALOG WHEN SHOW STATUS IS SELECTED PROBLEM SUMMARY : Runtime error occurs in CDM CC Domain when clicking 'Selected/Show Status' function. The failing event occurs in the following scenario: a - CC Domain window is active b - The User add a Workstation by command line c - The User verifies the status (selecting 'Show Status' function) before to have refreshed the CC Domain window. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE PROBLEM CONCLUSION: Changed Dialog internal process. PTRNBR: 4U00491 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: CDM DIALOG, MESSAGE ANXE5101 RC 0 REASON 4311 NOT EXPLICATIVE PROBLEM SUMMARY : In the CDM dialog, when trying to install an object already installed in INRU status, on a target workstation, results as message ANXE5101 with the following information: rc=0 and reason=4311. This message does not help User to identify problem source. COMPONENTS CHANGED OR ENHANCED: CDMD.EXE ANXEDTMS.MSG ANXEDTMS.HLP PROBLEM CONCLUSION: A new message has been defined for this situation. This message is now displayed instead of ANXE5101 rc=0 reason=4311: ANXE5486 Install request failed for Object 'object-name' on WorkStation 'workstation.name' because it is already Installed No Removable in Use. Use Install/Force to install anyway. PTRNBR: 4U00494 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: CDM START WAITS UNTIL THE LOCKUP IS UNLOCKED PROBLEM SUMMARY : Running on top OS/2 2.11 at FixPak XR_A091 (OS2KRNL dated 12/1/95) or later versions, the CDM START command waits indefinitely until the LOCKUP is UNLOCKED. COMPONENTS CHANGED OR ENHANCED: ANXCLNUP.DLL PROBLEM CONCLUSION: Corrected internal process. PTRNBR: 4U00496 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: NvDM/2 V2.1 DOES NOT INSTALL ON TOP DB2/2 V2.1 PROBLEM SUMMARY : The NvDM/2 V2.1 does not install anymore on DB2/2 because of changes introduced with V2.1 of this last. . In brief the changes of DB2/2 V2.1 versus its V1.x that impacted NvDM/2 V2.1: . a - New SYSLEVEL extension for DB2/2 Server (DB2 instead of SQC) b - SQLLIB main directory no anymore in PATH c - NULL: parameter not accepted anymore by SQLABIND API d - STARTDBM and STOPDBM commands no supported anymore (later discussion with DB2/2 Development lead to have DB2/2 V2.1 to support these commands along with the old DBM command interpreter). COMPONENTS CHANGED OR ENHANCED: SBODY.EXE PMSBODY.EXE ANXIIDDB.DLL ANXIICMS.BND ANXIIDTB.BND ANXIISIN.BND ANXIIPIN.BND ANXIITAB.BND PROBLEM CONCLUSION: The NetView DM/2 V2.1 installation programs have changed as follows: . a - Search for SYSLEVEL.SQC or SYSLEVEL.DB2, concatenated with environment variable DB2PATH, to determine if DB2/2 is installed. b - solved by item "a" c - Pass "NULL" instead of "NULL:" parameter to SQLABIND API d - Try to invoke DB2START when failing with STARTDBM PTRNBR: 4U00499 APARNBR: PJ19583 PTFNBR: XREFP01 EXTERNAL SYMPTOM: NvDM/2 V2.1 FAILS TO START DUE STATEMENT MISPLACED INTO CONFIG.SYS PROBLEM SUMMARY : . Reference: PMR 3351X B395 C000 (Questar service corp.) PMR 5X723 B395 C000 (Questar service corp.) . NvDM/2 Device drivers not found at first reboot on C: drive after installing OS/2, NvDM/2, and LAPS in maintenance mode on D: drive. COMPONENTS CHANGED OR ENHANCED: BODY.EXE PROBLEM CONCLUSION: The failing event reported over the referenced PMR was due a misplacement of the following statement into CONFIG.SYS at the end of a NvdM/2 installation in production environment: DEVICE=C:½OS2½INSTALL½ANXACTVF.SYS C:½OS2½INSTALL½anxlockf.acl What happened was that the above statement was inserted after the following CONFIG.SYS line, because of a mischeck about any installed IFS, while should be placed as first line, in case of bootable fixed partition formatted as FAT, or just after the first existing IFS statement other than NvDM/2 one: IFS=C:½IBMNVDM2½BIN½anxifcom.ifs The mischeck was due to wrong handling of mixed case statements into CONFIG.SYS now corrected adding a C function that translates the line in analysis to upper case before to execute the check.