|
We had a problem with DHCP not starting automatically. It was caused by a conflict with BOOTP. Change your BOOTP attributes to not autostart. And do NOT use STRTCPSVR *ALL. Because it can't. Rob Berendt ================== Remember the Cole! "Roger Vicker, CCP" <rvicker@vicker.com To: Midrange List <MIDRANGE-L@midrange.com> > cc: Sent by: Subject: Problem starting DHCP on V4R4M0 owner-midrange-l@mi drange.com 03/05/01 04:21 PM Please respond to MIDRANGE-L Hello, Has anyone had a problem (and hopefully a solution) with DHCP not starting automatically (CHGDHCPA AUTOSTART(*YES)) and not being able to start it manually/explicitly with adopted authority? I have a customer that wants to use DHCP but can only get it to start by being a member of QSECOFR. We have tried a program that adopts QSECOFR without any success. The job log shows: From module . . . . . . . . : QTODDCNV From procedure . . . . . . : qtod_IssueMessage__FPcT1ie Statement . . . . . . . . . : 852 Message . . . . : DHCP attributes file missing or not valid. Cause . . . . . : DHCP requires an attributes file. The file that it tried to open was /QIBM/USERDATA/OS400/DHCP/DHCP.ATTRIB, and it encountered an error. The error code was 3401. An error code of 0 indicates that the DHCP attributes file exists but that the data was not valid. Any other error code indicates a file I/O error occurred. Because of this error, an attempt was made to restore the attributes file from default values but that was unsuccessful also. Without the attribute information, processing was unable to continue. Recovery . . . : Use the command "WRKLNK '/QIBM/USERDATA/OS400/DHCP/DHCP.ATTRIB'" and if the DHCP attributes file Authority is: Data Opt User Authority *PUBLIC *RX However I did check the full path and found: Data Opt User Authority *PUBLIC *EXCLUDE QSECOFR *RWX QTCP *RX Thanks, Roger Vicker, CCP -- *** Vicker Programming and Service *** Have bits will byte *** www.vicker.com *** Where do you find 100 talking invertebrates? The US Senate +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.