×
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.
On 07 Jun 2012 11:39, Brian Piotrowski wrote:
I created a table in the SQL Interpreter using this statement:
CREATE TABLE SPSL/PLC_WORK2
( PLANTCODE CHAR ( 1) NOT NULL WITH DEFAULT
, LREFNUM INT NOT NULL WITH DEFAULT
, <<SNIP>>
I received this message back:
Table PLC_WORK2 in SPSL created but was not journaled.
<<SNIP>>
Presumably that was SQL7905 "Table &1 in &2 created but could not be
journaled." [text from v5r3 USEnglish]
The diagnosed\warned-of condition can be resolved by issuing a
request to: STRJRNPF SPSL/PLC_WORK2 /* name a journal for JRN() */
For automatic journaling on future CREATE TABLE into library SPSL,
either create a journal object named QSQJRN in the library SPSL, or
implement the "Default Journal" feature for the library [be that via the
QDFTJRN *DTAARA object in the target library, or whatever its
replacement; I believe that is the Start Journal Library (STRJRNLIB)
command with effects presented by DSPLIBD command]. At least the former
[use of QSQJRN] should be described in both the "Cause" and "Recovery"
sections of the 1="Display message text" from the request to: DSPMSGD
SQL7905 QSQLMSG
Regards, Chuck
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.
midrange.com
