[Info-vax] Coding Excel files...

[Jan-Erik Soderholm]

David Froble wrote 2014-02-13 01:06:
> VAXman- @SendSpamHere.ORG wrote:
>> In article <ldg9ak$soa$1 at news.albasani.net>, Jan-Erik Soderholm
>> <jan-erik.soderholm at telia.com> writes:
>>> {...snip...}
>>>
>>> Not at all. The data is usualy in some Rdb table (written by the
>>> Cobol applications) and some batch job runs Python and creates
>>> the XLS files (using the Python Rdb interface and the Excel
>>> tools). Sometimes the Cobol code submittes the batch job or
>>> it can be done using a table trigger.
>>
>> Good grief.  I hate COBOLlers LIB$SPAWNing shit all over the place.  I hate
>> it even more when the LIB$SPAWN a SUBMIT command.
>>
>
> There can be conditions where spawning a sub-process or a detached process
> is reasonable.  With a SPAWN/NOWAIT you can move on to other work while
> <whatever> completes in the background.
>
>>
>>> Another Cobol app writes data to a table and a table trigger
>>> submittes a job that uses the Python PDF ("ReportLab") tools
>>> to create PDF reports (accessed through the web server, WASD).
>
> Don't know what "table trigger" is ???

Are you asking what a trigger is?

http://en.wikipedia.org/wiki/Database_trigger


>
>> So, if I've read you right, you're running a Python script in a BATCH job to
>> convert tabled data to XLS.
>>
>
> I'd stay out of the batch queues, but that's just me...

I think they are a nice tool to get things done.

>