| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 306.1 | What line? | UTRTSC::BOSMAN | We're just sugar mice in the rain | Tue Mar 24 1992 07:14 | 3 |
| What line? Did they use substitution, a lexical or else?
Sjaak.
|
| 306.2 | Yeah, more details please! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Mar 24 1992 09:03 | 8 |
| What version?
We did have a bug like this during V3.0 development, but it was fixed
again. I remember the person who found it had brought an application
that worked on V2.4 along to one of our test days and found we'd broken
it.
Graham
|
| 306.3 | example | GIDDAY::ROWED | | Thu Mar 26 1992 02:56 | 35 |
|
The customer faxed me the following examples:
Enter CMD:get #dcl_command = 'test = '01234567890123456789012345678901
2345678901234567890123456789012345678901234567890123456789012345678901
23456789012345678901234567890123456789"' *
Enter CMD:get #dcl_command
%OA-I-LASTLINE, test = "0123456789012345678901234567890123456789012345
6789012345678901234567890123456789012345678901234567890123456789012345
6789012345678901234567890123456789"
Enter CMD:get oa$dcl = #dcl_command
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\01234567890123456789012345678901234567890123456789"\
Enter CMD:get #dcl_command = #dcl_command:128 '"' **
Enter CMD:get oa$dcl = #dcl_command
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\"\
Enter CMD:get #dcl_command = #dcl_command:127 '"' ***
Enter CMD:get oa$dcl = #dcl_command
Enter CMD
** line is 187 characters.
** line is 129 characters.
** line is 128 characters.
Deb
The above line is 187 characters long. Fails when OA$DCL is called.
Enter CMD:get #dcl_command = #dcl_command:128 '"'
|
| 306.4 | Broken in Script too? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Mar 26 1992 09:08 | 10 |
| Does this also happen when the code is in a script, or only at the
"Enter CMD:" prompt?
I ask this because we made a chnage in V3.0 to allow command line
recall at the CMD prompt, and hence we have buffered the command lines.
Perhaps we buffered them too small....
Any comments Paul?
Graham
|
| 306.5 | Change ' into " | UTRTSC::BOSMAN | We're just sugar mice in the rain | Thu Mar 26 1992 13:43 | 12 |
| Hi,
� Enter CMD:get #dcl_command = 'test = '01234567890123456789012345678901 ���
You should change this (to define the local DCL symbol test) into:
v
Enter CMD:get #dcl_command = 'test = "01234567890123456789012345678901
And (ofcourse) end the line with "' (double quote - single quote)
Sjaak.
|
| 306.6 | Don't blame me! | IOSG::TALLETT | Mit Schuh bish hi | Mon Mar 30 1992 09:02 | 11 |
|
RE: .4
Enter CMD: get oa$dcl = #dcl_command
I just pass ->get oa$dcl = #dcl_command<- to the command dispatcher
without expanding anything, so its not GOLD-7 buffering getting in
the way! Whew, you had me worried for a minute!
Regards,
Paul
|
| 306.7 | Waiting for more information folks !! | GIDDAY::SETHI | Man from Downunder | Mon Mar 30 1992 09:25 | 9 |
| G'day All,
I have just taken over this call from Deb she is on holiday. The
customer is having problems in Name Data he sent me the form and not
the text as I had requested. Guess what the form is corrupted I have
asked him to send me the text this time. So it's a case of Waiting ...
Waiting ... etc.
Sunil
|
| 306.8 | Too large a number | WAYLND::HOWARD | Hail to the Redskins! | Mon Mar 30 1992 18:30 | 6 |
| I think .5 has the answer. DCL looks at the value and if it is a
number, it treats it as a number. I seriously doubt that it can handle
a number of 187 digits! You're approaching agoogle here. How long can
DCL symbols be if they are text?
Ben
|
| 306.9 | About 1000... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Mar 30 1992 18:36 | 9 |
| Re .8
<<< How long can DCL symbols be if they are text?
That was the first thing I thought of checking. At the $ prompt, they
can be about 1000 characters, depending on whether you just define
them, or try to do any lexical functions on them.
Graham
|
| 306.10 | oops | WAYLND::HOWARD | Hail to the Redskins! | Mon Mar 30 1992 19:26 | 7 |
| RE;.8
It was worth a try! I do see the error in:
> a number of 187 digits! You're approaching agoogle here. How long can
That's way past 100 places!
|
| 306.11 | Text of the form that is causing the problem | GIDDAY::SETHI | Man from Downunder | Tue Mar 31 1992 06:16 | 169 |
| G'day All,
I have managed to get the text for the form and here it goes :-)
I will highlight the OA$DCL with ^^^^^^^^^^^^^^^
|||||||||||||||
Customization Management
Element Print as of 01:06pm on 31-Mar-1992
Element name: BT_PAGER_SEND Type: FRM
Language: BRITISH
Description: Argument form called when a user wants to send a pager mess.
Created on: 30-Mar-1992 11:46am by FOLEYT
Last Modified on: 30-Mar-1992 11:46am by FOLEYT
Made live on:
Reference: Live: N
Application: BT_PAGER Digital: N
Status: Element is locked by FOLEYT
Last User: FOLEYT
Details:
This form gets called from the Create option on BT_PAGING_INDEX. It
gets required information from the user and then sends the pager
message by calling the paging system in the ALL-IN-1 subprocess
File contents:
! FMS Form Description Application Aid
! Version V2.4
FORM NAME='BT_PAGER_SEND'
AREA_TO_CLEAR=1:23
WIDTH=80
BACKGROUND=CURRENT
;
TEXT (2,31) 'Send a Pager Message '
BOLD
;
TEXT (5,1) 'Recipient:'
;
TEXT (5,36) 'Priority:'
;
TEXT (7,1) 'Pager Message:'
;
TEXT (14,2) 'Enter details and press RETURN'
;
ATTRIBUTE_DEFAULTS FIELD
CLEAR_CHARACTER=' '
NOAUTOTAB BLANK_FILL NOBLINKING NOBOLD NOREVERSE
NOUNDERLINE NODISPLAY_ONLY ECHO NOFIXED_DECIMAL
LEFT_JUSTIFIED NOSUPERVISOR_ONLY NOSUPPRESS NOUPPERCASE
;
FIELD NAME='BT_BEUTENAME' (5,17)
PICTURE=12'X'
UPPERCASE RESPONSE_REQUIRED
;
FIELD NAME='PRIORITY' (5,47)
PICTURE='X'
;
FIELD NAME='PAGER_MESSAGE_1' (8,1)
PICTURE=80'X'
AUTOTAB RESPONSE_REQUIRED
;
FIELD NAME='PAGER_MESSAGE_2' (9,1)
PICTURE=80'X'
AUTOTAB
;
FIELD NAME='PAGER_MESSAGE_3' (10,1)
PICTURE=80'X'
AUTOTAB
;
FIELD NAME='PAGER_MESSAGE_4' (11,1)
PICTURE=80'X'
AUTOTAB
;
FIELD NAME='PAGER_MESSAGE_5' (12,1)
PICTURE=62'X'
;
ORDER BEGIN_WITH = 1
NAME='BT_BEUTENAME'
NAME='PRIORITY'
NAME='PAGER_MESSAGE_1'
NAME='PAGER_MESSAGE_2'
NAME='PAGER_MESSAGE_3'
NAME='PAGER_MESSAGE_4'
NAME='PAGER_MESSAGE_5'
;
NAMED_DATA INDEX=1 NAME='.TYPE'
DATA='ARG /OVERLAY/HARD="Send a Paging Message"' ;
NAMED_DATA INDEX=2 NAME='.TYPE'
DATA='/POST="IFEXIT\XOP ~~BUILD_DCL_COMMAND~~\GET OA$DCL=#DCL_COMMAND"' ;
NAMED_DATA INDEX=3 NAME='BT_BEUTENAME' ^^^^^^^^^^^^^^^^^^^^^^^^^
DATA='/HARD="Recipients Beute Username"' ; |||||||||||||||||||||||||
NAMED_DATA INDEX=4 NAME='BT_BEUTENAME'
DATA='/VALID=<.IF BT_CORPHONE_ENTRY.BT_PAGERNUM[BT_BEUTENAME] NES '''' THEN ' ;
NAMED_DATA INDEX=5 NAME='BT_BEUTENAME'
DATA=' OA$VAL_SET_VALID ELSE DISPLAY That entry was not recognized (Press HELP' ;
NAMED_DATA INDEX=6 NAME='BT_BEUTENAME'
DATA=' for Help)' ;
NAMED_DATA INDEX=7 NAME='BT_BEUTENAME'
DATA='/RSE_RECOG=BT_CORPHONE_ENTRY.BT_BEUTENAME WITH .BT_BEUTENAME BEGINNING' ;
NAMED_DATA INDEX=8 NAME='BT_BEUTENAME'
DATA=' BT_BEUTENAME AND .BT_PAGERNUM NES ''''' ;
NAMED_DATA INDEX=9 NAME='PRIORITY'
DATA='/HARD="Pager Message Priority"' ;
NAMED_DATA INDEX=10 NAME='PRIORITY'
DATA='/VALID=OA$TABLE:"1,2,3"' ;
NAMED_DATA INDEX=11 NAME='PRIORITY'
DATA='/RECOG=OA$TABLE:"1 - URGENT,2 - Important,3 - Non-Urgent"' ;
NAMED_DATA INDEX=12 NAME='~~BUILD_DCL_COMMAND~~'
DATA='GET #DCL_COMMAND = ''BTpage/PRIORITY='' PRIORITY '' '' ' ;
NAMED_DATA INDEX=13 NAME='~~BUILD_DCL_COMMAND~~'
DATA=' BT_CORPHONE_ENTRY.BT_PAGERNUM[BT_BEUTENAME]' ;
NAMED_DATA INDEX=14 NAME='~~BUILD_DCL_COMMAND~~'
DATA=' '' "'' PAGER_MESSAGE_1 PAGER_MESSAGE_2 PAGER_MESSAGE_3 PAGER_MESSAGE_4 ''"''' ;
END_OF_FORM NAME='BT_PAGER_SEND' ;
Form: BT_PAGER_SEND
1 2 3 4 5 6 7 8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
--------------------------------------------------------------------------------
1| |1
2| Send a Pager Message |2
3| |3
4| |4
5|Recipient: Priority: |5
6| |6
7|Pager Message: |7
8| |8
9| |9
10| |10
11| |11
12| |12
13| |13
14| Enter details and press RETURN |14
15| |15
16| |16
17| |17
18| |18
19| |19
20| |20
21| |21
22| |22
23| |23
--------------------------------------------------------------------------------
12345678901234567890123456789012345678901234567890123456789012345678901234567890
1 2 3 4 5 6 7 8
Thanks
Sunil
|
| 306.12 | Use OAMAILBOX | SNOC02::ZORBASSTUART | NULL Junior | Tue Mar 31 1992 07:32 | 10 |
|
I had the same problem with GET OA$DCL doing a similar sort of thing.
Instead of issuing the 'BTpage/<parameters>' from ALL-IN-1, put it in a
command procedure and use OAMAILBOX/DCLMAILBOX to retrieve the
parameter list from ALL-IN-1.
Cheers,
Stuart 'making a trunc call' Zorbas
|
| 306.13 | Use DCL continuation lines | IOSG::TALLETT | Just one more fix, then we can ship... | Tue Mar 31 1992 07:58 | 14 |
|
Even simpler, why not do:
GET OA$DCL = "DIR/D-"
GET OA$DCL = "ATE"
or in your case, break the symbol at some arbitary place and stick
in a "-".
Still sounds like a bug to be QARed though, if it breaks
applications.
Regards,
Paul
|