× 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: Accessing/changing PDM defau
  • From: D.BALE@xxxxxxxxxxxxx
  • Date: Wed, 10 Jan 2001 11:22:00 -0500

Mike, there are two reasons why I'd prefer to just email the source to those
who request it.

#1 is that we're talking over 100 lines of code (which probably isn't too bad?)
#2 is that the majority of my RPGLE source statements extend to column 80,
which will split lines when our email server or the list server chops line
lengths to 72 (or whatever it is).

Mike, I will send the code to you in a few minutes.  Other interested parties
may email me privately at D.Bale@Handleman.com .  SPECIFY whether you're on
V3R2 or not (V3R2 requires shorter field names); if you don't, I'll send the
V3R2 source.

Oh, and one other caveat:  Using a high-level "tool" such as DmpSysObj to
retrieve this type of information is subject to OS release dependencies,
although this particular utility has worked successfully on several releases
(can't remember which ones, though the same code works on v3r2 and v4r4, so
one could imply that all the ones in between are OK as well).

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Thanks for that. I originally tried doing a DMPSYSOBJ but couldn't find where
the option file was stored, so couldn't work out if this was the way to go.
Could you paste your source code here as it would be of interest? Thanks in
advance.

Mike

D.BALE <D.BALE@handleman.com>@INTERNET@midrange.com> on 10/01/2001 14:16:17
Please respond to MI400 <MI400@midrange.com>@INTERNET
Sent by: owner-mi400 <owner-mi400@midrange.com>
To: mi400 <mi400@midrange.com>@INTERNET
cc:
Subject: Re: Accessing/changing PDM defau

The MI gurus may have figured how to handle it more gracefully, but I have a
utility that retrieves the PDM defaults and puts them in a data area.
Updating the defaults is not possible through the interface I use to retrieve
them, which is basically:

   DmpSysObj  Obj( &User ) Context( QSYS ) Type( 0E ) SubType( C4 )

Since you seem to require updating the PDM defaults outside of PDM, you
probably wouldn't be interested, but I would be happy to share the source code
for formatting the DmpSysObj output into a data area.  I.e.:

  Data area . . . . . . . :   $PDMDFTSDA
    Library . . . . . . . :     QTEMP
  Type  . . . . . . . . . :   *CHAR
  Length  . . . . . . . . :   256
  Text  . . . . . . . . . :   PDM Defaults for user BALED

             Value
  Offset      *...+....1....+....2....+....3....+....4....+....5
      0      '*SRCLIB   YYN 1QBATCH    *LIBL                DJBL'
     50      'IB    QAUOOPT   YYY                               '
    100      '                                                  '
    150      '                                                  '
    200      '                                                  '
    250      '      '

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Anyone know any way of retrieving/changing the defaults from PDM (other than
pressing F18 on a PDM screen!!!)?
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.