[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irnbru::ims_api

Title:
Moderator:IRNBRU::MACKENZIE
Created:Wed Jul 10 1991
Last Modified:Tue May 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:289
Total number of notes:1527

186.0. "IMS Master Problems on Ultrix & OSF/1..." by OZROCK::THOMAN (OSS Engineering, Australia - "DTN" 736 0146) Thu Aug 18 1994 10:26

T.RTitleUserPersonal
Name
DateLines
186.1Does the <nodename> (*) mean "the current node" ??OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Thu Aug 18 1994 12:3915
186.2Ownership of master files... on OSF/1OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Fri Aug 19 1994 12:5244
186.3Server Attributes Syntax In CDSOZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Fri Aug 19 1994 12:5732
186.4RE: Master Crash on MIPS/Ultrix from .0 (copy core from 59.348:/public/ims/)OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Mon Aug 22 1994 12:0840
186.5Master doesn't recognise names for processes that sl_connect_a_p("") then sl_declare_p("<name>",..)OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Mon Aug 22 1994 13:3243
186.6It is not meant to!PLADDA::DRIVETTMon Aug 22 1994 14:3326
186.7OZROCK::TURNERThe Playroom - alive 'til fiveTue Aug 23 1994 11:5911
186.8PLADDA::DRIVETTTue Aug 23 1994 12:4121
186.9OZROCK::TURNERThe Playroom - alive 'til fiveTue Aug 23 1994 13:5021
186.10More concerns....OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Thu Aug 25 1994 13:4833
186.11Some general responsesPLADDA::DRIVETTFri Aug 26 1994 19:01225
186.12Answers RE: .11OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Tue Aug 30 1994 13:2773
186.13More concerns for the list...OZROCK::THOMANOSS Engineering, Australia - &quot;DTN&quot; 736 0146Tue Aug 30 1994 13:4065
186.14Some answersCLOUZO::GALVANJean-Philippe GALVAN - Sophia-Antipolis - 828-5621Wed Aug 31 1994 11:5714
186.15OZROCK::TURNERThe Playroom - alive 'til fiveThu Sep 01 1994 05:509
186.16OSF IMS V1.3 Master Concerns - Writes to the screen. - Boot start. - Attribute SettingOZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Mon Nov 07 1994 04:2977
186.17ULYSSE::FINKAMon Nov 07 1994 13:5024
186.18Can the master be changed to perform the "dce_login" itself?OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Mon Nov 14 1994 07:0531
186.19Continued from .18 (Re-authenticating, & start as root !)OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Mon Nov 14 1994 11:4764
186.20ims_cds_attributes (OSF/1)OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Thu Nov 24 1994 11:5716
186.21How/Where does the Master cache CDS information ?OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Fri Nov 25 1994 05:0542
186.22it dsn matterELIS::TBARRETTWaiting for the van to comeFri Nov 25 1994 11:047
186.23Check your DMQ group.initPLADDA::DRIVETTFri Nov 25 1994 11:2816
186.24Entry in CDS & QCT Allowed/Correct ?OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Mon Nov 28 1994 04:1727
186.25PLADDA::DRIVETTMon Nov 28 1994 11:4534
186.26Syntax for the PAMS_NODE attribute - where does it look?OZROCK::THOMANTry telling that to the Project Managers of today, &amp; they won't believe you. (Yorkshire accent)Tue Nov 29 1994 09:3732
186.27OZROCK::TURNERThe Playroom - alive 'til fiveWed Nov 30 1994 02:1810
186.28Usage of master "send" and the -166 errorOZROCK::THOMANMr. InstallationTue Dec 13 1994 07:4057
186.29Master client and server queriesIRNBRU::MACKENZIETue Dec 13 1994 11:2437
186.30re 186.28PLADDA::DRIVETTTue Dec 13 1994 11:4030
186.31Changed based on feedbackAZUR::GALVANJean-Philippe GALVAN - Sophia-Antipolis - 828-5621Wed Dec 14 1994 10:438
186.32Thanks, & more...OZROCK::THOMANMr. InstallationThu Dec 15 1994 07:5532
186.33MASTER CLIENT DOES NOT USE MASTER SERVER WHEN DOING SENDAZUR::GALVANJean-Philippe GALVAN - Sophia-Antipolis - 828-5621Thu Dec 15 1994 11:3831
186.34I discovered that..OZROCK::THOMANMr. InstallationFri Dec 16 1994 06:5531
186.35PLADDA::DRIVETTFri Dec 16 1994 11:3546
186.36Time to continue this note..OZROCK::THOMANBring back &quot;Eddie The Eagle Edwards&quot; !!Wed Mar 12 1997 12:2369
	
	Can I please make a few requests for the next release of
	the Master on Digital UNIX ?

	firstly,

	When the user types "masterc start" an .intmp file is created
	which contains a line of the form:

		<INPUT FILE>   >   <OUTPUT FILE>

	Can this please be change to:

		<INPUT FILE>   >&   <OUTPUT FILE>

	so that stderr is also directed to the OUT FILE.



	2ndly, when users try to stop servers, errors like

		-166

	meaning the server isn't running, OR

		<some success stmt followed by>
		CLIENT NOT AUTHORISED

	meaning there is no

		..../<server>_organic.sec 

	file in existance.

	
	Speaking of security files, is it 

		<node>::<user> 

	OR
	
		<user>::<node>

	??


	I assume either can be "*" so it means

		"User X is permitted from Any node"

	in the case where the <node> part is an asteris, 

	OR,

		"Any user on node N is permitted"

	in case where the <user> part is an asteris.



	Also, we notice the master_server writes to the screen
	for errors such as the <INPUT> file is not executable
	when a START is attempted.

	Sorry for being a bit pedantic 
	
	Thanks,

	Craig.
186.37The never ending Master noteIRNBRU::MACKENZIEWed Mar 12 1997 16:1365
>>	When the user types "masterc start" an .intmp file is created
>>	which contains a line of the form:
		<INPUT FILE>   >   <OUTPUT FILE>
>>	Can this please be change to:
>>		<INPUT FILE>   >&   <OUTPUT FILE>
>>	so that stderr is also directed to the OUT FILE.

We shall provide an option for this. The default behaviour will not change.

>>	2ndly, when users try to stop servers, errors like
>>		-166
>>	meaning the server isn't running, OR
>>		<some success stmt followed by>
>>		CLIENT NOT AUTHORISED
>>	meaning there is no
>>		..../<server>_organic.sec 
>>	file in existance.

If you are saying these aren't meaningful enough then we agree. We're hoping
to be able to overhaul these in the next major release.
	
>>	Speaking of security files, is it 
>>		<node>::<user> 

Yes

>>	OR
>>		<user>::<node>

No

>>	I assume either can be "*" so it means
>>		"User X is permitted from Any node"
>>	in the case where the <node> part is an asteris, 

Yes

>>      OR
>>		"Any user on node N is permitted"
>>	in case where the <user> part is an asteris.

Still Yes
Basically the * is a wildcard that can be used on either side. So

	*::SYSTEM

means any system account on any machine and

	IRNBRU::*

means any user on node IRNBRU.

>>	Also, we notice the master_server writes to the screen
>>	for errors such as the <INPUT> file is not executable
>>	when a START is attempted.

That is intended.

>>	Sorry for being a bit pedantic 
	
Suggestions for improvements are always welcome.

Cheers,
Dave M.