× 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: V4R4 Gotcha new Journal
  • From: "R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>
  • Date: Wed, 8 Mar 2000 08:08:54 -0500

QSQJRN is the standard, IBM supplied journal name for any SQL - Created
collection.

The question I would have, is what is the program doing that requires the
journal name and library? Under normal circumstances, the relationship
between the file and the journal is managed by those two objects, not by
programming.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"

-----Original Message-----
From: Garcia Rich (SYS1RXG) <sys1rxg@ups.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Tuesday, March 07, 2000 9:49 PM
Subject: V4R4 Gotcha new Journal


>Did anyone experience the following:
>
>When upgrading to V4R4 there is a new system object which is placed within
>QSYS2 it is called QSQJRN, the problem here is that we had any application
>code to a journal with the same name(QSQJRN) in V4R3 but in a library
called
>D101AA.
>When we started the application it basically blew up in the certification
>phase of the new Operating System because the application coded to this
>journal and specified *LIBL and not D101AA. Look out for this it is not
>stated in any of the V4R4 documentation as a new to the system and I feel
>that IBM has taken away from one of there best feature and that is to be
>able to code to *libl and not hardcode libraries.
>
>Have Fun
>
>Rich Garcia
>AS400 Systems Programmer
>+---
>| 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
>+---
>

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


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.