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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

3010.0. "oa$yn spanish translation" by ISIDRO::TORRECILLA () Thu Jul 15 1993 11:40

    Hello,
    
    I am using ALLIN1 3.0, the spanish version and there seems to be a
    problem with symbol OA$YN:
    
    When you add a user to the profile, the field MNODE (MULTI_NODE) only
    lets you put "Y" or "N", if you put "Y" to say you want that user to be
    entered in the NETWORK.DAT, this doesn't happen, it doesn't add the
    user to the NETWORK.DAT.
    
    If you go to SM, MANAGE MESSAGING, MAD, and create that user to be
    entered in the NETWORK.DAT, the field MNODE only accepts "S" or "N",
    ("S" is the spanish "Y"). This way that user becomes part of the
    NETWORK.DAT. 
    
    There seems to be a problem with the symbol OA$YN, sometimes accepts
    "Y" and others "S".
    
    I would like to solve this problem so that when I create a user and say
    I want him to be part of NETWORK.DAT filling up the MNODE field, he is
    being added as happened in ALLIN1 2.4.
    
    Does anybody had this problem with a different language version, and
    how was it solved??
    
    Thanks,
    
    Nieves

T.R	Title	User	Personal Name	Date	Lines
3010.1	probably a buggette...	IOSG::TYLDESLEY		`Thu Jul 15 1993 13:00`	23
	Nieves, I think you may have found a problem here. The SM forms e.g. the one I think you are using (SM$CREATE$PROFILE), now, religiously (;-), use /VALID=OA$YN:SM$_YN. SM is very rarely translated, so SM$_YN is probably on your system "Y,N". Now the update network profile script that is called from SM$CREATE$PROFILE - smnetupdt.scp - does some comparisons with OA$Y, which will be translated. So, the network update fails. When you create a user normally (C CU) a different script is used - sm_modify_network.scp - which handles this OK, by taking Profile values which are always stored as Y/N. Also, the MM MAD route is ok, because the form NETWORK also uses /VALID="OA$YN". I think this needs an SPR, in fact, I suspect we may already have one. The fix will probably involve calling a modified version of sm_modify_network, rather than changing the SM$CREATE$PROFILE form. In fact, that's probably why it has never been done ;-). Cheers, DaveT
3010.2	edit user problem	ISIDRO::TORRECILLA		`Thu Jul 15 1993 13:55`	11
	Dave, I forgot to tell you, exactly the problem is when you edit a user you have already created. No problem when you create it, it adds the new user to the network.dat, but if you want to change a field as the telephone number, or something, this modification isn't written to the network.dat. Do you know if there is an SPR already to fix this? Thanks for you quick answer Nieves
3010.3	same script	IOSG::TYLDESLEY		`Thu Jul 15 1993 15:18`	17
	Nieves. I think the same argument still applies. SM$PROFILE, which is used to edit an account, also calls SMNETUPDT. this script has lines like: GET #PRO_MULTI = MULTI_NODE - and then .IF #PRO_MULTI EQS OA$Y THEN - I suspect that this is where your edit is failing. Try running the edit with <debug on. I think you'll find it happens in the XOP ~~POST_CHANGE~~. I've scanned my list of to-be-fixed, but no network update ones come immediately to view (it could of course be hidden by a misleading title!). Better submit SPR. Cheers, DaveT
3010.4		PETRUS::HOFMANN	Stefan Hofmann, LC Frankfurt, ISE	`Thu Jul 15 1993 15:19`	9
	Well, Dave, I think it's covered by a couple of other SPRs that Ingo sent you since the end of translation. Nieves, this has not yet been reported for any other language. Maybe our support department (=0.4 persons) will provide a fix in PETRUS::DIAMOND$BUGFIXES$PUBLIC:[language] Stefan