Spooling to DocMgr with custom DES


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Robert G Laurin on January 07, 2013 at 13:15:17:

It is Monday and a new year...

I'm trying my best to get rid of QSPOOL and am trying to switch to DocMgr.

I've trace printing to the DocMgr spool using (Spool Message)...

Here's my finding and some questions....

- When I use 'Print (1) (SPOOL Message=MyMessage$)' I get an extra blank line in the DocMgr Job
- When I use 'Print (1) (LS);(Spool Message=MyMessage$)' I get an extra (CR) before my first line
- I looked in the online documentation... (SPOOL MESSAGE) is not documented in the 'S' mnemonics, but it is found in the 'M' mnemonics.
- There is a (TR) but the wiki is a bit confusing... Almost sounds like the CR/LF is suppressed forever, I thought it was for a single print/format.
- I traced the DES, it does not seems to use either the (SPOOL MESSAGE) nor return the Job Number or Name. What I get after an INPUT (#) after the close is the name of the temporary file.

I need my custom DES to know the actual job name (from the SPOOL MESSAGE) to properly handle the file. It needs all the job info to properly decide what to do with the spooled document. Need program name, who ran it and the content of the spool message.

Today, I feel real dumb asking these questions again... I must be getting old.


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]