═══ 1. Open NetDoor Help ═══ "There are things that are known, and things that are unknown; in between, the doors" William Blake OpenDoor - Start the Network Door client environment OpenDoor is run when you start a NetDoor client system. The tasks that it performs will vary, depending on the system configuration, but in general OpenDoor does the following: o Checks for adequate system swap space o Determines the access method (ie. OS/2 LAN requester, NFS, CD-ROM) and starts it, if necessary o Logs on to the LAN (if LAN-attached) o Gets the name of the least-used NetDoor fileserver o Connects to the NetDoor fileserver o Tries alternate domains or servers if the first attempts are not successful o Attaches the NetDoor drive o Loads and registers REXX function libraries o Runs any site exit programs (XCOREUP.CMD) that are found in the \LOCAL subdirectories on the NetDoor drive o Starts USERINIT.CMD o Starts applications contained in the NetDoor startup folder if they've been recently updated. o Makes back-up copies of some files that are critical to NetDoor o Starts the maintenance program to apply NetDoor changes o Logs machine configuration information to a NetDoor administrator disk o Displays a site message-of-the-day, if there is one o Logs all OpenDoor messages to OPENDOOR.LOG Command Syntax: OPENDOOR

Where: /d = run in debug mode; display extra diagnostic information /p = prompt for logon/connection information (logon for NetBios only) /o = display "Set Options" dialog shortly after application begins /nouserinit = do not start USERINIT.CMD or the NetDoor startup folder /nomaint = do not start the maintenance program (MAINT.EXE) OpenDoor Main Window The main window contains a menu bar, a current status area, control buttons, and a list of previous OpenDoor messages. The window size and position are saved when you close the application. Halt button Halts OpenDoor processing. If pressed again, or while already halted, will terminate OpenDoor. Technical Note - most of the real work that OpenDoor performs, other than window handling, is done in a secondary thread. When the Halt button is pressed the first time, OpenDoor suspends the secondary thread. If the Continue button is then pressed, the secondary thread resumes processing. The status area, to the left of the halt button, indicates the current state of the secondary thread ("Halted" or "Running"). Continue button Resumes OpenDoor processing. The Continue button is only active if OpenDoor is halted. OpenDoor Messages OpenDoor issues messages that chart its progress. The latest message always appears in the current status area near the top of the window. Previously issued messages appear in a scrollable list at the bottom of the window, and are also written to a log file on your disk. Users may choose to hide the message list by re-sizing the OpenDoor window, or by pressing the re-sizing buttons (the down and up-arrow buttons). Each message begins with a message identifier, followed by explanatory text. The message identifier is in the form COUnnnnS, where: COU = message prefix nnnn = the message number S = a one-letter message suffix that identifies the message type There are five types of messages. Each message type may be color-coded while displayed within the current status area, if you have enabled color messages in the OpenDoor Options dialog. Message types o Informational, message suffix= I, color= green. Ordinary status messages. Most messages will be of this type. o Debug, message suffix= D, color= green. Special messages that are only displayed if the debug option is enabled (although they are always written to the log file). They contain detailed technical information which will not be of much interest (or even make much sense) to the general user, but provide additional detail about the program's progress that may be useful to support personnel when debugging problems. o Warning, message suffix= W, color= yellow. Issued when a minor error condition is detected. o Error, message suffix= E, color= red. Issued when a significant error condition is detected. User may be asked whether to Halt or Continue. o Fatal Error, message suffix= F, color= red. A condition occurred that prevents the program from continuing. Additional processing is terminated. Fatal errors will have to be corrected before OpenDoor will function correctly. What to do if a problem occurs 1. Review the messages in the list box, paying particular attention to warning or error messages. Use the "Search" selections under the "Actions" menu to help locate the warnings and errors. 2. If possible, attempt to correct any problems described in the message list. 3. If the problem persists, send a copy of the message log file to your local support group, along with a note describing any other symptoms that you noticed. The first message in the list will tell you the file name of the message log. See Also: Warning Messages, Error Messages, Logon Return Codes, Return Codes from IBM LAN Requester, OpenDoor Debugging Guide ═══ 2. Set Options Help ═══ OpenDoor provides a number of run-time options, which you can change to match your needs via the "Set Options" dialog. The options that you set with this dialog will be remembered and used, unless they are overridden with OpenDoor command-line parameters. Automatically close main window When checked, the main window automatically closes itself when OpenDoor processing completes. If not set, you will have to close the window yourself upon completion. Run USERINIT.CMD and startup folder When checked, the OpenDoor will attempt to start USERINIT.CMD and any programs found within your NetDoor startup folder, after it has connected to the NetDoor drive. Prompt for connection/logon information (logon for NetBios only) If not checked, OpenDoor will automatically log you on and connect you to the NetDoor drive, unless your logon settings have not been saved. When checked, the OpenDoor will always display the "Network Logon" dialog. Display debug messages If not checked, OpenDoor only displays status messages. When checked, OpenDoor will also display "debug" messages. Most users will not need to display the debug messages, since they contain detailed technical information which will usually be more confusing than helpful. Debug messages are always written to the OpenDoor log file, regardless of this setting. Color-code status messages If checked, OpenDoor color-codes the current status messages. Informational and debug messages are written in green, warning messages in yellow, and error messages in red. Ok button Exit the dialog, and save the options settings. Cancel button Exit the dialog, but don't save the options settings. ═══ 3. Network Logon Help (for NetBios only) ═══ Logon to the network (for NetBios only) This dialog prompts for logon information, including your network user id and password. The password field is protected, and will display an asterisk for each character entered. This dialog also lists the network domains and NetDoor servers that OpenDoor can connect to. Note - some NetDoor installations may not require a logon password (depending on how your local LAN administrator has set up your userid). Change button Displays the Set Connections dialog, which allows you to change the list of domains and NetDoor servers that OpenDoor can attach. Logon button (for NetBios only) Closes the dialog window, and proceeds with the logon/connection attempt, using the userid and password information that was entered. Cancel button Closes the dialog window, and halts with the logon/connection attempt. The Continue button on the main window will be activated, in case you decide to proceed with the logon/connection attempt. Save settings Save the userid, domains, and servers listed within this dialog. Save password Save the current password. Note - Password saving is a site option, which may be disabled by the local NetDoor administrator. The first time you use OpenDoor, the "Save password" button will not be available. After you make your first connection to a NetDoor server, the "Save password" button will be visible (if enabled at your site). See Also: Logon Return Codes (for NetBios only) ═══ 4. Network Logon Help (for TCP/IP NFS users only) ═══ Mounting network drive (for TCP/IP NFS users only) This dialog lists the NFS data servers and NetDoor servers to which OpenDoor can connect. Change button Displays the Set Connections dialog, which allows you to change the list of NFS data servers and NetDoor servers to which OpenDoor can attach. Cancel button Closes the dialog window, and halts with the connection attempt. The Continue button on the main window will be activated, in case you decide to proceed with the connection attempt. Save settings Save the NFS data servers, and NetDoor servers listed within this dialog. ═══ 5. Set Connections Help ═══ Setting network connection information One of the main tasks that OpenDoor performs is to connect you to a network domain, and attach a NetDoor drive from a fileserver. This dialog allows you to specify the domains and NetDoor servers that OpenDoor may use. Much of this information may have been previously set up for you when NetDoor was installed on your system. Logon Domains (for NetBios only) Your userid may have been authorized to logon to any one of several network domains, even though IBM Lan Requester only permits you to logon to one domain at a time. To help make sure that you get logged on to the "best" domain (ie. one with the fastest or most reliable connection), OpenDoor allows you to define domain groups. During OpenDoor processing, it first attempts to log you on to a domain in group 1. If the first logon attempt fails, it will try another domain within group 1. If none of the logon attempts for domains in group 1 is successful, it will then attempt to logon to a domain within group 2, etc. OpenDoor does not attempt to log on to domains within a group in the exact order listed. Instead, it randomly picks domains from within a group, in order to spread workload more evenly among eligible domain servers. Note: OpenDoor will query each of the domains until it finds the NetDoor configuration file SERVERS.COR, so at least one of the domains in one of the domain groups must be a NetDoor domain. NetDoor Servers This entry field allows you to define a list of potential NetDoor servers to connect to. Only one NetDoor fileserver will be "attached", but you may list several, in case the first one is not available during the connection attempt. If you specify an asterisk '*' in this field, OpenDoor will pick the least-used available fileserver. See Also: Technical Notes, OpenDoor group rules ═══ 5.1. Technical Notes ═══ o OpenDoor determines the least-used server by reading the COUNETB.DAT file on one of the NetDoor domains. The domain uses LUSACCT.EXE to build the COUNETB.DAT file. o If COUNETB.DAT is not available, or is outdated, OpenDoor will still connect to a NetDoor server, but will not be able to accurately balance the server load. o The SERVERS.COR file on the NetDoor domain(s) is used as a "nickname" file. It is used to help resolve NetDoor server and alias names. It must be available or OpenDoor will not be able to complete its processing. ═══ 5.2. OpenDoor group rules ═══ 1. At least one domain must be a NetDoor domain, ie, must have a COUDATA alias (CORESTUF for IBM internal sites), but the NetDoor domain can be in any one of the four groups. 2. Groups are ordered from 1 to 4; domains within a group (separated by spaces) have equal weight. 3. Domains within a group will be tried in random order until logon succeeds or the group is exhausted. (logon for NetBios only) 4. Groups will be tried in order from 1 to 4 until logon succeeds or all groups are exhausted. Blank groups are skipped. 5. If all domains in all groups are exhausted, OPENDOOR reports an error, sleeps, then retries the cycle from the beginning. Examples of domain group usage within the "Set Connections" dialog: Case 1 - Two NetDoor domains, Domain Controllers are on same ring: Group 1: Domain1 Domain2 Group 2: Group 3: Group 4: Case 2 - Two NetDoor domains, one is "preferred" (ie. one is closer on the network, perhaps) Group 1: Domain1 Group 2: Domain2 Group 3: Group 4: Case 3 - Two NetDoor domains, plus a user domain which should be used if online Group 1: UserDom1 Group 2: Domain1 Domain2 Group 3: Group 4: Case 4 - Case 2 and 3 combined Group 1: UserDom1 Group 2: Domain1 Group 3: Domain2 G4: ═══ 6. Warning Messages ═══ Each message begins with a message identifier, followed by explanatory text. The message identifier is in the form COUnnnnS, where: COU = message prefix nnnn = the message number S = a one-letter message suffix that identifies the message type Warning Messages COU1402W Warning: Error while trying to read file xxxxxxx; RC= nn Explanation: The file xxxxxxx could not be read. Possible causes: file or path does not exist, or could not be opened due to sharing violation. COU1403W Directory xxxxxxx does not exist. Creating it... Explanation: The subdirectory xxxxxxx was not found. The application will attempt to create the subdirectory. COU1406W Warning: Unable to open message log file, xxxxxxx ... RC= nn Explanation: The file xxxxxxx could not be opened for output. Possible causes: path does not exist, or could not be opened due to sharing violation. Messages will not be logged to disk. The return code contains the open error code. COU1407W Warning: System swap drive has only nn MBytes available. Explanation: OS/2 may not have enough space on your swap disk (ie. SWAPPER.DAT) to meet system requirements. COU1410W Timeout waiting for Halt or Continue button to be pressed. Defaulting to Continue... Explanation: A warning or error message was issued earlier that asked whether you wanted to halt or continue processing. You did not respond, so the application continues by default. COU1411W Timeout waiting for Halt or Continue button to be pressed. Defaulting to Halt... Explanation: A warning or error message was issued earlier that asked whether you wanted to halt or continue processing. You did not respond, so the application halts by default. COU1412W Already logged on to domain. Network logon RC= nnnn. OPENDOOR process continues... Explanation: You are already logged on, and you can only log on to one domain at a time. Processing will continue, and an attempt will be made to connect you to an OPENDOOR fileserver. COU1413W Warning: Error during network logon of Userid xxxxx to domain xxxxx. RC= nnnn. Checking other domains..." Explanation: An error occurred during the network logon attempt. OPENDOOR will attempt to log you on to an alternate domain (if any were entered in the "Set Connections" dialog). The return code contains the IBM LAN logon return code; see the "Return Codes" help text for further information. COU1414W Authorization error during LOGON Userid xxxxx. RC= nnnn. Logon dialog will be displayed. Please verify that you have entered the correct userid and password. Explanation: An error occurred during the network logon attempt. You may have entered an incorrect userid or password. The logon panel will be displayed in order to give you an opportunity to re-enter the userid and password. The return code contains the IBM LAN logon return code; see the "Return Codes" help text for further information. COU1415W Warning: Error connecting to NFS dataserver on xxxxx. RC= nn. Checking other domains... Explanation: An error occurred while trying to mount the remote drive that contains the OPENDOOR nicknames file (SERVERS.COR). OPENDOOR will attempt to connect to an alternate data server (if any were entered in the "Set Connections" dialog). COU1420W Access denied for server xxxxxx. NET USE RC= nnnn Explanation: An attempt to attach (ie. NET USE) an OPENDOOR fileserver failed. OPENDOOR will attempt to connect to an alternate file server (if any were entered in the "Set Connections" dialog). Possible cause: you are not authorized to use the fileserver alias. Check with your local LAN administrator. COU1421W Network server path xxxxxx cannot be found. NET USE RC= nnnn Explanation: An attempt to attach (ie. NET USE) an OPENDOOR fileserver failed. OPENDOOR will attempt to connect to an alternate file server (if any were entered in the "Set Connections" dialog). Possible cause: server is not available (offline). Check with your local LAN administrator. COU1422W Network alias name xxxxxx cannot be found. NET USE RC= nnnn Explanation: An attempt to attach (ie. NET USE) an OPENDOOR fileserver failed. OPENDOOR will attempt to connect to an alternate file server (if any were entered in the "Set Connections" dialog). Possible cause: domain or server is not available (offline), or the alias is not defined to current domain. Check with your local LAN administrator. COU1423W Network drive d: already assigned. NET USE RC= nnnn Explanation: An attempt was made to attach (ie. NET USE) a drive, using a drive letter that is already in use. COU1424W Unable to locate help file xxxxxx. Help will not be available. Explanation: Online help file could not be found. If you experienced this error, and are now reading this help text via the online help facility, then a miracle has occurred. COU1425W Unable to allocate memory for clipboard data. Clipboard not available. Explanation: You asked to copy to the clipboard, but OS/2 could not find enough memory to hold the clipboard data. Possible causes: swap drive has filled, or no swap drive was specified in CONFIG.SYS. COU1426W Unable to access a NetDoor drive. Will wait a bit and try again. Press Halt if you wish to terminate. Explanation: an error occurred while trying to attach the NetDoor drive from the fileserver. An earlier error or warning message should provide further details about the access failure(s). If you do not wish to try to attach the drive again, press the Halt button. COU1427W Function not yet loaded from DLL. Try again later... Explanation: You asked to perform a function before the necessary DLL has been loaded. If you try again a little later, it will probably work. COU1428W Network drive d: already assigned. MOUNT RC= nnnn Explanation: An attempt was made to attach (ie. MOUNT) a drive, using a drive letter that is already in use. COU1500W 1500W Halt or cancel button pressed. OpenDoor processing has paused. Press Halt again to terminate, or Continue to resume. Explanation: You either pressed the "Halt" button on the main window, or the "Cancel" button on the Network Logon dialog. Processing has paused, and will not resume until you press the "Continue" button. If you press "Halt" again, the application will terminate. COU1512W All logon attempts failed. Will wait a bit and try again. Press Halt if you wish to terminate. Explanation: Unable to logon to any of the domains listed in the "Set Connections" dialog. An earlier error or warning message should provide further details about the logon failure(s). If you do not wish to try to logon again, press the Halt button. COU1513W All attempts to connect to the NFS dataserver failed. Will wait a bit and try again. Press Halt if you wish to terminate." Explanation: Unable to connect to any of the domains (NFS dataservers) listed in the "Set Connections" dialog. An earlier error or warning message should provide further details about the failure(s). If you do not wish to try again, press the Halt button. ═══ 7. Error Messages ═══ Each message begins with a message identifier, followed by explanatory text. The message identifier is in the form COUnnnnS, where: COU = message prefix nnnn = the message number S = a one-letter message suffix that identifies the message type Error Messages COU1701F Error: Unable to create subdirectory. Continue or Halt?" Explanation: OPENDOOR attempts to verify the existence of certain NetDoor subdirectories. If they do not exist, it attempts to create them. This error is issued when the directory could not be created. If you continue, you may experience other errors, later in the process. COU1806F Error: Modules xxxxx.EXE and xxxxx.DLL are at different release levels. This will result in errors during processing. OpenDoor processing terminated. Explanation: two interdependent modules are at incompatible release levels. Processing cannot continue. Possible causes: try to verify that you do not have multiple copies of the modules. There may have been a failure during COUFIX or NetDoor installation. Contact your local NetDoor administrator. COU1810F Fatal error: Unable to create semaphore in subroutine xxxxxx. RC= nn Explanation: OpenDoor creates an OS/2 "semaphore" to coordinate its activity. It was unable to do so, and cannot continue. Possible causes: swap drive has filled, no swap drive was specified in CONFIG.SYS, or an OS/2 error has occurred. COU1811F Fatal error: Unable to load LAN Requester functions, UPM.DLL. RC= nn. OpenDoor processing terminated. Explanation: OpenDoor uses LAN functions from the UPM.DLL library in order to perform a LAN Requester logon. Possible causes: either UPM.DLL could not be found within the LIBPATH, or else there was an error while loading it. COU1813F Fatal error: Unable to load NetDoor connection library COUxxx.DLL. RC= nn. OpenDoor processing terminated. Explanation: OpenDoor uses functions from DLLs in order to access the network. It was unable to load the necessary DLL. Possible causes: either the DLL could not be found within the LIBPATH, or else there was an error while loading it. COU1814F Error: Unable to open file xxxxxx. RC= nn. OpenDoor processing terminated. Explanation: OpenDoor reads configuration information from its .INI file. If this file cannot be located, or opened, the application terminates. Possible causes: Error in your OS2.INI file; failure to point to the correct application .INI file. COU1815F Error: Password for Userid xxxxx has expired. RC= nnnn. Please contact your LAN administrator. OpenDoor processing terminated. Explanation: the network logon attempt failed because your password has expired. Contact your LAN admininistrator to have your password reset. COU1822F Fatal Error: Unable to access domain server via GetDCName function. Cannot read SERVERS.COR. Unable to continue OpenDoor processing. Explanation: no NetDoor domain server was available. Possible causes: none of the domains listed in the "Set Connections" dialog is a NetDoor server, or else all of the NetDoor domains listed are offline or inaccessible. COU1826F Unrecoverable error while trying to access a NetDoor drive. OpenDoor processing terminated. Explanation: no NetDoor file server was available. Earlier warning or error messages should provide additional details about the failure(s). COU1830F Fatal Error: unable to find nickname entry, or unable read server nickname file xxxxx. RC= nn from GetNickName(). OpenDoor processing terminated. Explanation: OpenDoor reads a nickname file (SERVERS.COR) to determine the names of eligible fileservers. The nickname file either could not be located, or the nickname could not be found. See the logfile for additional debug data. Possible causes: nickname file contents in error, or nickname file not found. COU1900F Halt requested by user. Terminating further OpenDoor processing. Explanation: User has requested termination by pressing the "Halt" button. COU1901F Fatal Error: Unable to allocate memory for application's pWinData structure. Terminating." Explanation: Memory for an internal data structure could not be obtained. Possible causes: swap drive has filled, no swap drive was specified in CONFIG.SYS, or an OS/2 error has occurred. COU1902F Couldn't create main window. Possible cause: Window already exists, or PM resources exhausted. WinGetLastError RC= nnnn (defined in PMERR.H). Possible causes: another instance of the application was started earlier (this can happen if it is started via both STARTUP.CMD and the startup folder). COU1903F Fatal Error: Couldn't create background thread. Terminating. Explanation: Most OpenDoor processing occurs in a secondary OS/2 thread. The thread could not be created. Possible causes: swap drive has filled, no swap drive was specified in CONFIG.SYS, or an OS/2 error has occurred. ═══ 8. Logon Return Codes (FBxx) ═══ Network Logon Error Codes from IBM LAN Requester: The following error codes may be returned by the IBM LAN Requester, during a network logon attempt: UPM_OK 0 /* Successful. */ UPM_LOG_INPROC 0xFB01 /* Another logon is in process. */ UPM_BAD_TYPE 0xFB02 /* Bad remotetype. */ UPM_NOMEM 0xFB03 /* Cannot allocate required memory. */ UPM_LOG_FILE_NOT_FOUND 0xFB04 /* An execute file could not be found. */ UPM_FAIL_SECURITY 0xFB05 /* User not logged, failed security clearance. */ UPM_BAD_PARAMETER 0xFB06 /* A parameter passed was invalid. */ UPM_BAD_AUTHCHECK 0xFB07 /* Authcheck was not valid. */ UPM_LOG_CANCEL 0xFB08 /* User has canceled from the logon panel. */ UPM_NOT_LOGGED 0xFB10 /* A logon has not occured for this userid. */ UPM_LOGGED 0xFB12 /* A domain logon is currently active. */ UPM_SYS_ERROR 0xFB13 /* An unexpected system error. */ UPM_OPEN_SESSIONS 0xFB14 /* The domain logoff failed, The domain logon has active sessions. */ UPM_ULP_LOADED 0xFB15 /* The local logon failed, a local logon with a user logon profile is active. */ UPM_LOGGED_ELSEWHERE 0xFB16 /* The domain logon failed, the userid is already logged on the domain. */ UPM_PASSWORD_EXP 0xFB17 /* The users password is expired. */ UPM_UNAVAIL 0xFB18 /* The logon failed, The remote node or server could not be contacted to process the logon request. */ UPM_ACTIVE 0xFB19 /* The domain logon or logoff failed, a domain logon, logoff or net command is in process. */ UPM_SS_PWDEXPWARNING 0xFB20 /* The local logon succeeded. The users password is expired. */ UPM_SS_BUSY 0xFB21 /* The local logon failed. The Secure Shell was busy. */ UPM_SS_DEAD 0xFB22 /* The local logon failed. The Secure Shell has terminated unexpectedly. */ UPM_ERROR_MORE_DATA 0xFB23 /* More data is available, the buffer provided is not large enough. */ ═══ 9. Return Codes from IBM LAN Requester ═══ Errors that occur while trying to connect a NetDoor drive via IBM LAN Requester are usually defined in the file \IBMLAN\NETSRC\H\NETERR.H (available as part of the LAN programmers toolkit). ═══ 10. OpenDoor Debugging Guide ═══ Locating the error log The OpenDoor error log is an ascii file which can be browsed with any standard editor. It contains detailed information about the flow of data and the internal function calls used during OpenDoor processing. It also contains all the informational and error messages that were issued the last time OpenDoor ran. If a user reports a failure during OpenDoor processing, get the error log name from the first line in the "OpenDoor Message Log" listbox. This listbox appears at the bottom of the OpenDoor main window (you may have to re-size the window if the user has hidden the listbox). See Also: Warning Messages, Error Messages, Logon Return Codes, Return Codes from IBM LAN Requester Sample OpenDoor error log Below is an example OPENDOOR.LOG file, showing a successful logon and connection to an IBM LAN Server NETDOOR environment. The messages can vary a bit, depending on the local configuration, but in general will be similar to the ones shown below. Numbers are shown to the left of messages that may be of special interest during debugging. For an explanation of the numbered items, see the list which follows the sample log. 1) 13:53:22 ....> COU1004I v0.31b: Messages are being logged to file D:\pmcoreup\OPENDOOR.LOG 13:53:22 ....> ----- Date: 28 June 1993, 13:53:22 EDT OS/2 v210 ----- 13:53:22 ...>> COU1200D Running OPENDOOR executable D:\pmcoreup\OPENDOOR.EXE 13:53:22 ....> COU1001I Initializing OpenDoor. 13:53:22 ...>> COU1200D ChkSwapDrive( 0087:000C) 2) 13:53:22 ...>> COU1207I System swap drive G: has 38 MBytes available 13:53:22 ...>> COU1200D readProfile( 0087:000C, 1) 13:53:23 ...>> COU1202I Reading D:\CORE\COREDATA\CORE.INI. 13:53:23 ...>> COU1200D readProfile WinPosition= # 116 446 752 444 -10346 4096 3) 13:53:24 ...>> COU1200D COUENV values: REMOTE= W:\; LOCAL= D:\CORE; SYSTEM= D:\CORE\COREDATA 4) 13:53:24 ...>> COU1200D COUENV values: OLDCONFIG= D:\CORE\OLDCONFG; SNAME= CORE; 13:53:24 ....> DATARES= CORESTUF 13:53:24 ...>> COU1200D readProfile(): 6 bytes processed from pProData->Flags 13:53:24 ...>> COU1203I Verifying contents of OpenDoor settings. 13:53:24 ...>> COU1200D VerifyProfileData( 0087:000C ) 13:53:24 ...>> COU1200D VerifyDir( 0087:000C, D:\CORE\OLDCONFG) 13:53:24 ...>> COU1200D VerifyDir( 0087:000C, D:\CORE) 13:53:25 ...>> COU1205I Function library COUILR.DLL loaded. 13:53:25 ...>> COU1200D GetCore(0087:000C) 5) 13:53:25 ...>> COU1200D .EXE version= 0.31b; .DLL version= 0.31b 13:53:25 ....> COU1028I Accessing network. 6a) 13:53:25 ...>> COU1200D pProData->LDomains= CORELAB | YKCOD01 YKCOD02 | YKCOD03 13:53:26 ....> | YKCOD04 13:53:26 ...>> COU1200D Net Logon Dialog Flag2= 9 7) 13:53:27 ...>> COU1200D Net Logon Dialog OK selected; pProData->CServers= * 13:53:28 ...>> COU1200D writeProfile(0087:000C, 1) 13:53:28 ...>> COU1200D Saving settings in D:\CORE\COREDATA\CORE.INI... 13:53:28 ...>> COU1200D writeProfile WinPosition= # 116 446 752 444 -10346 13:53:28 ...>> COU1200D writeProfile SAVEPW nick= YES?? 6b) 13:53:29 ...>> COU1200D WinDlgBox LDomains= CORELAB | YKCOD01 YKCOD02 | YKCOD03 13:53:29 ....> | YKCOD04 13:53:30 ...>> COU1200D DomainGroup 1 = CORELAB 13:53:30 ...>> COU1200D DomainGroup 2 = YKCOD01 YKCOD02 13:53:30 ...>> COU1200D DomainGroup 3 = YKCOD03 13:53:30 ...>> COU1200D DomainGroup 4 = YKCOD04 8) 13:53:30 ...>> COU1200D NetLogon( 0087:000C, SLAUSON, password, CORELAB ) 13:53:30 ...>> COU1210I Loading LAN Requester functions from UPM.DLL... 13:53:31 ....> COU1011I Issuing network logon to LAN domain CORELAB for Userid 13:53:31 ....> SLAUSON. This may take a while; please wait... 9) 13:53:32 ...>> COU1200D NetWkstaGetInfo LS version= 3.0 10) 13:54:29 ....> COU1012I Network logon complete. RC= 0 13:54:29 ...>> COU1200D Connected domain= CORELAB 13:54:30 ....> COU1013I Password for UserId SLAUSON is 10 days old. 13:54:30 ...>> COU1200D ConnectCoreDrive( 008F:000C, W:, CORELAB) 13:54:30 ...>> COU1200D FindServersCor( 008F:000C, CORELAB, , ) 13:54:30 ...>> COU1200D GetDCName( CORELAB, \\CORELABS, 256); RC= 0 13:54:31 ...>> COU1200D Checking \\CORELABS\CORESTUF\SERVERS.COR 11) 13:54:31 ...>> COU1200D FindServersCor( 008F:000C, CORELAB, \\CORELABS, \\CORELABS\CORESTUF\SERVERS.COR); 13:54:31 ....> RC= 0 12) 13:54:31 ...>> COU1200D FindLeastUsedServer( 008F:000C, \\CORELABS, ) 13:54:31 ...>> COU1200D DosOpen \\CORELABS\CORESTUF\COUNETB.DAT; oRc= 0 13:54:31 ...>> COU1200D Timestamp= 152315; CompTime= 133931 13:54:34 ...>> COU1200D DosOpen \\CORELABS\CORESTUF\COUNETB.DAT; oRc= 0 13:54:34 ...>> COU1200D Timestamp= 152315; CompTime= 133934 13:54:36 ...>> COU1200D DosOpen \\CORELABS\CORESTUF\COUNETB.DAT; oRc= 0 13:54:36 ...>> COU1200D Timestamp= 152315; CompTime= 133936 13:54:36 ...>> COU1200D \\CORELABS\CORESTUF\COUNETB.DAT is out-of-date; using 13:54:36 ....> SERVERS.COR instead... 13) 13:54:37 ...>> COU1200D RC 0= GetNickName( \\CORELABS\CORESTUF\SERVERS.COR, CORELAB, 13:54:37 ....> SERVERS, CORELABS WATAD01S) 14) 13:54:37 ...>> COU1200D RC 0= GetNickName( \\CORELABS\CORESTUF\SERVERS.COR, CORELABS, 13:54:37 ....> ID, CORE) 15) 13:54:37 ...>> COU1200D DoNetUse( 008F:000C, W:, \\CORELABS\CORE) 13:54:37 ....> COU1021I Attempting to access NetDoor alias \\CORELABS\CORE as 13:54:38 ....> drive W:... 16) 13:54:38 ....> COU1022I NetDoor drive attached successfully. 13:54:38 ...>> COU1200D NetWkstaGetInfo.wki10_computername= C-FOOD 13:54:40 ...>> COU1200D RegisterAndRun( RXUTILS, RxLoadFuncs, NULL ); RC= 0 13:54:41 ...>> COU1200D RegisterAndRun( REXXUTIL, SysLoadFuncs, NULL ); RC= 0 13:54:41 ...>> COU1200D LocalExit( 008F:000C ) 13:54:41 ...>> COU1200D LocalExit() checking for W:\LOCAL\XCOREUP.CMD 13:54:41 ...>> COU1200D LocalExit() checking for W:\LOCAL\SERVER\XCOREUP.CMD 13:54:41 ...>> COU1200D LocalExit() checking for W:\LOCAL\DOMAIN\XCOREUP.CMD 13:54:41 ...>> COU1200D LocalExit() checking for W:\LOCAL\COUPLET\XCOREUP.CMD 13:54:42 ...>> COU1200D LocalExit() checking for W:\LOCAL\SITE\XCOREUP.CMD 13:54:42 ...>> COU1200D LocalExit() checking for W:\LOCAL\COMPLEX\XCOREUP.CMD 13:54:42 ....> COU1033I Starting W:\LOCAL\COMPLEX\XCOREUP.CMD... 13:54:42 ...>> COU1200D doStartSession( 008F:000C, W:\LOCAL\COMPLEX\XCOREUP.CMD, 13:54:42 ....> (null)) 13:54:43 ...>> COU1200D doStartSession RC= 0 13:54:43 ...>> COU1200D LocalExit() checking for W:\LOCAL\REGION\XCOREUP.CMD 13:54:43 ....> COU1033I Starting D:\CORE\COREDATA\USERINIT.CMD... 17) 13:54:44 ...>> COU1200D doStartSession( 008F:000C, D:\CORE\COREDATA\USERINIT.CMD, 13:54:44 ....> (null)) 13:54:44 ...>> COU1200D doStartSession RC= 0 13:54:44 ...>> COU1200D DTSuserinitdoneDTS atom created. 18) 13:54:44 ...>> COU1200D doStartSession( 008F:000C, W:\STARTOBS.EXE, "" 13:54:45 ....> /CONTENTS /TCPIP) 13:54:45 ...>> COU1200D doStartSession RC= 0 13:54:46 ...>> COU1200D BackupConfig( 008F:000C ) 13:54:46 ...>> COU1200D BackupFile(): Source= C:\OS2\OS2SYS.INI; Target= D:\CORE\OLDCONFG\OS2SYS.INI 13:54:47 ...>> COU1200D BackupFile(): Source= C:\OS2\OS2.INI; Target= D:\CORE\OLDCONFG\OS2.INI 19) 13:54:48 ...>> COU1200D BackupFile(): Source= D:\CORE\MYDLL\COUILR.DLL; Target= 13:54:48 ....> D:\CORE\OLDCONFG\COUILR.DLL 13:54:50 ...>> COU1200D DLL changed; backing up EXE: Source= D:\CORE\COREDATA\OPENDOOR.EXE; 13:54:50 ....> Target= D:\CORE\OLDCONFG\OPENDOOR.EXE 13:54:51 ...>> COU1200D COREFIX= W:\COREFIX.EXE 20) 13:54:51 ....> COU1033I Starting W:\COREFIX.EXE... 13:54:51 ...>> COU1200D doStartSession( 008F:000C, W:\COREFIX.EXE, (null)) 13:54:51 ...>> COU1200D doStartSession RC= 0 13:54:51 ...>> COU1200D ShowMOTD( 008F:000C ) 21) 13:54:52 ...>> COU1200D doStartSession( 008F:000C, W:\LOGSNET.EXE, C-FOOD NETBIOS 13:54:52 ....> \\CORELABS\CORESTUF\SERVERS.COR D:\CORE\COREDATA\OPENDOOR.LOG) 13:54:53 ...>> COU1200D doStartSession RC= 0 13:54:53 ....> COU1100I OpenDoor processing completed. 13:54:54 ...>> COU1200D writeProfile(008F:000C, 1) 13:54:55 ...>> COU1200D Saving settings in D:\CORE\COREDATA\CORE.INI... 13:54:55 ...>> COU1200D writeProfile WinPosition= # 116 446 752 444 -10346 22) 13:54:55 ...>> COU1200D writeProfile SAVEPW nick= YES Sample OpenDoor error log, explanation 1. Shows the version number of OPENDOOR.EXE and the name of the OPENDOOR error log. 2. Approximate free space remaining at the time OPENDOOR was running. If the swap space is low, this message will be followed by a warning message (COU1407W). 3. OpenDoor reads configuration data from it's INI file by calling a function in COUENV.DLL. These values will vary by site. If these values are incorrect for your site and installation, errors are likely to occur during subsequent OpenDoor or NetDoor processing. The values in this message provide the subdir names for the remote OpenDoor fileserver, the local OpenDoor (root subdir) subdir, and OpenDoor system data subdir, respectively. 4. The subdir names for the backup data subdir, and the local OpenDoor system name. 5. OPENDOOR.EXE has data interdependencies with it's DLL. If there is a version mismatch between the EXE and DLL, a fatal error (COU1806F) will be issued. 6. A list of domain groups from your NetDoor profile. 6b shows the domain groups after exiting the Logon/Connections dialog(s). 7. The user exited the logon dialog; at the time the dialog ended, the user had listed '*' as names of the OpenDoor servers to connect to. (Note: '*' means let the OpenDoor domain controller provide a list of available servers.) 8. This line shows the internal NetLogon function call, and the associated parameters. In this call, user SLAUSON will be logged on to domain CORELAB. The logon password is not saved in the log, for security reasons. 9. If you are running IBM LAN Requester, this line will display the version you are running. 10. Logon completed successfully. (for NetBios only) If there was an error during logon, you may see several logon retries, or an error message and error return code(depending on the circumstances). The error return code should provide a clue as to the cause of the failure. See the "Return Codes" section of the online help for more information. 11. The site administrator must set up a SERVERS.COR nickname file on each of the NetDoor domain servers. OpenDoor uses information from SERVERS.COR to determine the names of NetDoor servers, etc. This line shows that the internal function call, FindServerCor() completed successfully. In this example, for logon domain CORELAB, the domain controller name is \\CORELABS, and the alias which holds SERVERS.COR is \\CORELABS\CORESTUF. 12. OpenDoor looks on the domain controller for a "least-used-server" list, COUNETB.DAT. (For the TCP/IP case, the file is called COUNFS.DAT.) In this example, subsequent messages show that COUNETB.DAT was found, but that it was outdated. If COUNETB.DAT is outdated, OpenDoor ignores its information, and simply uses alternative information from SERVERS.COR. 13. OpenDoor uses the nickname file, SERVERS.COR, to retrieve a list of NetDoor servers that are defined for use with domain CORELAB. In this example, the nickname file indicates that servers "CORELABS" and "WATAD01S" are defined to the CORELAB domain. 14. OpenDoor has selected server "CORELABS" as the one to connect to. The nickname file, SERVERS.COR, contains the alias name for the NetDoor server (in this example, CORE). 15. Now that OpenDoor knows both the server and alias name, it can try to attach the NetDoor drive via a call to the DoNetUse() function. In this example, it will try to attach \\CORELABS\CORE as a W: drive. 16. \\CORELABS\CORE was attached successfully as drive W:. If this had failed, some retries would have been attempted, or a fatal error issued (depending on the nature of the error). 17. After OpenDoor has attached the NetDoor drive, it starts the user's copy of USERINIT.CMD, if it exists. 18. After OpenDoor has attached the NetDoor drive, it runs the STARTOBS program from the NetDoor drive, which will execute any programs in the NetDoor startup folder. 19. OpenDoor backs up certain critical system files to its backup subdirectory, if they have changed since the last backup. By doing this, it should be possible to recover from NetDoor software maintenance failures. In this example, OpenDoor has backed up both its own DLL and EXE file. 20. OpenDoor will start NetDoor software maintenance program. 21. OpenDoor runs LOGSNET.EXE from the NetDoor drive. LOGSNET will copy user configuration and status information to a NetDoor server, to assist administrators in problem tracking and determination. 22. OpenDoor will not save the user's logon password if the site administrator has disabled the "SavePW" feature. In this example, password saving is permitted. Password saving is disabled by including a :savepw.NO tag under :nick.!CONTROL in SERVERS.COR.