× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Comparing 2 printouts (before and after) ?
  • From: "Tim Truax" <truax@xxxxxxxxx>
  • Date: Wed, 15 Sep 1999 16:25:50 -0400

Thanks to all!
Buck, This is an excellent idea. I will see what I can come up with.  The only reason I have not done it as yet is because I thought there may have been an obscure existing AS400 method to produce the desired results.  Evidentally not because you guys would've known.
Thanks
:-) Tim & Dana Truax (-:
http://members.xoom.com/truax
----- Original Message -----
Sent: Wednesday, September 15, 1999 10:41 AM
Subject: RE: Comparing 2 printouts (before and after) ?

Tim,

You are right on the money with your procedure; all you need to do is wrap
it up in a CL program and off you go...  As an experiment, let's see if we
can't get some collaboration going on this: see if we can't build a freeware
utility we can give the AS/400 world!

>I would like suggestions on comparing the outputs
>of 2 dspfd commands to printer performed on the
>exact same file before then after a maintenance
>operation.  Here's how I do it now:
>
>1. dspfd file_a (before) to print queue.
>2. dspfd file_a (after) to print queue.
>3. cpysplf the 2 printouts to 2 different PF members.
>4. cpyf the 2 PF members to 2 different source PF members.
>5. then use STRPDM to do the 54 (compare).

You can roll all of this in a CL program.  Here's a start.  Look at the
defaults for CPYSPLF - they default to the current job.  By specifying
SPLNBR(*LAST) you can be assured that you are looking at the DSPFD you last
run, not an earlier one left lying about.  You'll need to add some variable
declarations and some MONMSGs to deal with errors on the CRTPF/ADDPFM and
CPYSPLF.  Post your program and we'll see if we can use the group to enhance
it!

CRTPF FILE(QTEMP/FD)
      RCDLEN(132)  
      MBR(*NONE)   
      MAXMBRS(2)   
      SIZE(*NOMAX) 
addpfm qtemp/fd old text('Original file description')
addpfm qtemp/fd new text('Current file description')

OVRPRTF *PRTF HOLD(*YES)

DSPFD &OLD_FILE OUTPUT(*PRINT)
CPYSPLF FILE(QPDSPFD) TOFILE(QTEMP/FD) TOMBR(OLD) SPLNBR(*LAST)
DLTSPLF FILE(QPDSPFD)

DSPFD &NEW_FILE OUTPUT(*PRINT)
CPYSPLF FILE(QPDSPFD) TOFILE(QTEMP/FD) TOMBR(NEW) SPLNBR(*LAST)
DLTSPLF FILE(QPDSPFD)

CMPPFM NEWFILE(QTEMP/FD) NEWMBR(NEW) OLDMBR(OLD)

DLTF QTEMP/FD

Buck Calabro
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.