[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

2169.0. "MGS NO 009E8312" by STKHLM::LUNDSTEDT () Thu Jan 28 1993 09:37

    
        Hello,
    
    My customer is trying to move documents from ALL-IN-1 to WPS DOS
    and this used to work fine until they upgraded WPS/DOS to 3.1. Now
    three users can't transfer documents using TD. They get an error message
    saying:     MSG NO. 009E8312   or MSG NO. 009E7312.
    
    Where can I find what these mean??
    
        Regards,
                              
    
        /*ANNA*
T.RTitleUserPersonal
Name		DateLines
2169.1a WPS oneIOSG::CARLINDick Carlin IOSG, Reading, EnglandThu Jan 28 1993 10:0712
    
    Anna
    
    My debug image tells me that 009E7312 doesn't exist, but 009E8312 is:
    
    %DDX-E-DHP_BPSP, Bad print setting found while parsing a WPS header
    
    I'll let someone else say what is the official way of finding out what
    these errors mean.
    
    Dick
2169.2THANKS!STKHLM::LUNDSTEDTThu Jan 28 1993 12:476
    Hi Dick!
    
    Thanks for the fast reply!! 
    
    /*ANNA*
2169.3Is this the *official* way?IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeThu Jan 28 1993 14:1717
    As I understand it, the offical way is as follows:
    
    	1) *Guess* which message file they are in, in this case DDXERR.MSG.
    
    	2) Compile the message file: $ MESSAGE/OBJECT DDXERR.MSG
    
    	3) Link it: $ LINK DDXERR
    
    	4) Add it to your message file list: $ SET MESSAGE DDXERR
    
    	5) Display it with the DCL message lexical:
    		$ WRITE SYS$OUTPUT F$MESSAGE( %X009E8312 )
    
    However I like Dick's idea of using a DEBUG image much better, since
    you get all the message files at once!
    
    Graham
2169.4what happened?GIDDAY::BURTChele Burt - CSC Sydney, DTN 7355693Wed Jul 14 1993 07:2519
Hello all,

What was the base-noter's result?
I have a custoemr who has reported the same problem under similar 
circumstances.

I tried doing a 
        2) Compile the message file: $ MESSAGE/OBJECT DDXERR.MSG

        3) Link it: $ LINK DDXERR
    
and ended up getting an error message before I could get any further along:
%LINK-W-USRTFR, image DISK$LPS:[ALLIN1.LLV_BRITISH]DDXERR.EXE;2 has no user 
transfer address

Thanks & regards,

Chele B
2169.5LINK/SHAREABLE ?IOSG::HULINIan Hulin, IOSG: REO, DTN 830-6141Wed Jul 14 1993 14:3112
   G'dye Chele,

   I think my esteemed colleague meant link it as a shareable image using 

   $ LINK/SHAREABLE

   LINK otherwise defaults to an executable image, hence its bellyaching about
   the lack of a transfer address.

   Cheers,

   Ian
2169.6Is that the real question?IOSG::CHINNICKgone walkaboutWed Jul 14 1993 15:168
    
    Ian,
    
    I thought Chele was asking about the DDX message as well...?
    
    You are correct about LINK/SHARE being required however.
    
    Paul.
2169.7tanjGIDDAY::BURTChele Burt - CSC Sydney, DTN 7355693Thu Jul 15 1993 06:0313
Hello,

duh. I have enough problems reading the letters, let alone between the lines 
and the spaces.

WRITE SYS$OUTPUT F$MESSAGE(%X009E8312)
%DDX-E-DHP_BPSP, Bad print setting found while parsing a WPS header

Ptui.

Thanks for your help.

Chele
2169.8By the wayIOSG::SHOVEDave Shove -- REO2-G/M6Wed Jul 21 1993 13:216
    Actually, you can skip the /SHARE in the LINK command and ignore the
    message about no transfer address (it is a warning, as you can see).
    
    You can still SET MESSAGE the resulting .EXE
    
    D.