| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
Hi,
I need to know how long can be the field "text" used as parameter by the
action routine.
At the customer site, one of the controlled system creates a very simple
event TEST sending a text string like the following to the OPCOM via a dcl
request command:
dd-mmm-yyyy hh:mm:ss.ccXX123456789012345678901234567890Fine <INSERT>=<TSK_PK
(total lenght: 81 chars).
The PCM gets this event and runs the standard console$mail action
routine. In this routine one the parameter passed from the PCM to the
routine and written to the mail message (it sould be the P4) is the field
"text" of the event.
When the customer read the received mail noted that the "text" field
was truncated to the character number 69. Supposing to have trapped the
wrong event, the event TEST has been regenerated on the controlled
system and the new mail reported the "text" field truncated to the
character number 71.
In both cases, the context displayed when the customer clicked twice on
the event in the multiline window seems fully captured.
I do not remember to have read on the PCM documentation any restriction
on the lenght of the parameters used by the action routine.
There is any other hidden reason on which the PCM (or maybe something
else) decides to truncate the string?
Any help is really appreciated.
Thanks in advance.
Anna
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1255.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Mar 28 1996 14:42 | 14 | |
No suprise that you saw the whole string in the Mutli-Line window. That
application uses the API which passes all known information to the action
routine. The command procedure interface does not. You have to tell it
what you want it to pass. Regardless, there is defintely a limit
on wht you can pass. Currently, the entire command line cannot exceed
132 characters as this is the size limit of a DCl *record* - notice I
did not say command which can be up to 1024 in length if I remember
right. The point here is that the command procedure interface needs to
be augmented so that it places one parameter per line and uses the
DCL "-" continuation character. I'll see that this gets placed on the
wish list.
Regards,
Dan
| |||||
| 1255.2 | other possible solution? | 47211::DPPS | The best get better | Fri Mar 29 1996 03:29 | 13 |
Dan,
thanks for the explanation. If I have understood well your answer, one
possible solution (until the command procedure will be augmented) could be
to write an action routine using an high level language and the provided
PCM-API to get the full text string.
Is it true?
Anna
| |||||
| 1255.3 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon Apr 01 1996 14:31 | 16 | |
> Dan,
>thanks for the explanation. If I have understood well your answer,
>one possible solution (until the command procedure will be augmented)
>could be to write an action routine using an high level language and the
>provided PCM-API to get the full text string.
>Is it true?
Yes. If you spend the time writing code then I would encourage you to
make that your permanent solution. It's far more efficient to use an
image based action routine. The first event that occurs will cause the
action routine process to start and subsequent events can then be
passed to running action routine.
Regs,
Dan
| |||||