Re: 6.11 weirdness


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

Posted by Grant Foraker on January 23, 2007 at 08:03:55:

In Reply to: Re: 6.11 weirdness posted by Barbara Brazil on January 22, 2007 at 11:14:52:

As far as I know all the other programs that run QREPORTS are OK. They have a different way of running some of their $ reports left over from the Q days.

Sequence of runs ...

1) PDER1 - updates the title lines of a set of reports, the first is $ACCT-00.

2) PDER2 - loads $ACCT-00 into common and runs REPORTS

3) REPORTS is mini version of *REPORT. If there's a $ in common then it runs QREPORTS, else it prompts for a $ name.

4) QREPORTS runs $ACCT-00 in foreground

Broke when we upgraded from 5.08 to 6.08. Started working when we retro'd to 6.08. Reupgraded to 6.11 and it's broke again.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 01/22/07 13:18:29 THE REPORTER - GENERATION VSN: 03.01 
 
 T00/P00 COPYRIGHT SIGNATURE SYSTEMS 1987 - 2003 


REPORT PREPARATION IN PROGRESS - $ACCT-00 ON PAC #FILES IS ON PAC

INPUT TIME.SHEET.B
ERROR = 43 - ACTUAL INPUT FILE NOT FOUND
PRINTER SP1
TITLE P A C I F I C S H I P R E P A I R

FATAL ERRORS EXIST. CANNOT PROCESS REPORT:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If the user tabs, they are returned to ...


 01/22/07 13:21:15 THE REPORTER - GENERATION VSN: 03.01 
 
 T00/P00 COPYRIGHT SIGNATURE SYSTEMS 1987 - 2003 


ENTER REPORT NAME: $ACCT-00
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If they enter the report, it will run correctly.

I've had the customer try several things.

1) recompile all the programs
2) make common the same size in PDER2 and REPORTS (12)
3) run PDER2 from READY
4) change PDER2 to run QREPORTS instead of REPORTS

He reports that all of these fail. He sent me his test data and I've been testing here and have had all of these work. However, the production method always fails for me.

Making an attempt at debugging I added SAVESOURCE to $ACCT-00. SAVESOUCE made no difference. If the test failed, no IBS file was generated. A partial ~ACCT-00 is created.

However, adding LOG makes things work. Commenting LOG out makes it fail.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note: LOG and PRINTER can't go to the same spooler.


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):






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