× 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.



You could try the following, it might just work.

You program must have observability.


Create a DB file with a record length of 528. You can use CRTPF and
specify a record length of 528. No source is required. Alternatively,
define a file in DDS with a field 528 bytes long.
Save your program to a save file.
Copy the save file to your new file (see below).
Use a file file viewing program (eg. DSPPFM) to examine your program.

The following RPG source code will provide you with a basis for copying
the save file to a DB file. This process also works in reverse!!

   H TEXT('Convert savfile to DB file')
   FSAVF      IP   F  528        DISK
   FDBFile    O    F  528        DISK
   ISAVF      NS  01
   I                                  1  528  FData
   ODBFile    D    01
   O                       FDATA              528

Change the file names to the names you used. You can use this program to
copy save files to database files.

If your program has observability you will often be able the view source
code in the save file. You should be able to veiw your I specs directly
on your screen. This method works better if the program you have is an
OPM program, not an ILE program.

Hopefully this will solve your problem.

Syd Nicholson



Dan Bale wrote:

>You might want to try asking this in the RPG list.  But, you haven't told us
>whether this input file is externally described or not.  I'm guessing you're
>referring to an internally described file.  Obviously, if it were externally
>described, you'd have figured out where to get the field specs for that.
>
>Also, just guessing here too, but it may make a difference whether the
>program object has had observability removed.
>
>There are decompilers out there, but they're nowhere near free.  Have you
>tried dumping the program object and seeing if you can find the input specs
>there?  (DMPOBJ)
>
>How 'bout this?  (Again, a real shot in the dark, don't know if this will
>work for your situation, YMMV...)  Have you considered putting a trigger on
>the file?
>
>Is there a reason why the software house *might* be hiding this information
>from you?  Sounds like it might be time to make a lot of noise.
>
>Dan Bale
>SAMSA, Inc.
>989-790-0507
>DBale@SAMSA.com <mailto:DBale@SAMSA.com>
>  Quiquid latine dictum sit altum viditur.
>  (Whatever is said in Latin seems profound.)
>
>
>-----Original Message-----
>From: midrange-l-admin@midrange.com
>[mailto:midrange-l-admin@midrange.com]On Behalf Of
>steven.donnellan@simonjersey.com
>Sent: Tuesday, March 19, 2002 10:33 AM
>To: midrange-l@midrange.com
>Subject: RTVRPGSRC
>
>
>Does anybody on the list know of a (free!) RTVRPGSRC utility
>OR
>Is there a way I can see the 'I' specs of an RPG Program so I can
>re-create the input file it's expecting? We don't have the source of the
>program, and the software house in question is either being stubborn or
>stupid when I ask this simple question.
>
>Steven Donnellan
>AS/400 Systems Manager
>IBM Certified Specialist - AS/400 Professional Operator
>Simon Jersey Ltd
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>




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.