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



the msg desc for sq9010 is from cmd: DSPMSGD RANGE(SQL9010) MSGF(QSQLMSG)
 Message ID . . . . . . . . . :   SQL9010
 Message file . . . . . . . . :   QSQLMSG
   Library  . . . . . . . . . :     QSYS
 Message . . . . :   RUNSQLSTM command failed.
 Cause . . . . . :   Errors were found while processing the source for the
   RUNSQLSTM command.  The listing print file is &1 in &2.
 Recovery  . . . :   Review the messages on the listing.  Either correct the
   problems or specify a higher severity on the ERRLVL parameter. Try the
   request again.
 Technical description . . . . . . . . :   The RUNSQLSTM command found
errors
   with a severity greater than the requested ERRLVL.

(this still doesn't tell all. make sure your interactive job is set for max
logging:
CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES)

then the dspjob, option 10 - or dspjoblog cmds should give more detail
(like file not found, or authority, or something)
also, the runsqlstm cmd defaults a printer file (qsysprt) - see if an error
page exists.
hth
jim franz

----- Original Message -----
From: "Richard Reeve" <richreeve@yahoo.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, December 26, 2001 10:07 AM
Subject: RUNSQLSTM problem


> --
> [ Picked text/plain from multipart/alternative ]
>
> Hi all.  I am having a problem running a simple SQL using the RUNSQLSTM
command.  Here is what I did.
>
> 1.  Crearted a source file called QSQLSRC in my library
>
> 2.  Created a source member in QSQLSRC called FIXFORNAM
>
>             UPDATE MDTMASSP SET FORNAM = '4' WHERE FORNAM = '9'
>
> 3.  I then created a CL called FIXFORNAM
>
> *************** Beginning of data *************************************
>              PGM
> /*  This is a one time fix that will be run to correct the formatting *
> /*  of the name when printing.                                        *
>              RUNSQLSTM  SRCFILE(CONSLTRR/QSQLSRC) SRCMBR(FIXFORNAM) +
>                           COMMIT(*NONE) NAMING(*SYS)  +
>                           SAAFLAG(*FLAG)
>              ENDPGM
> ****************** End of data ****************************************
>
> When I compile and run the above CL I get the following messages in my job
log;
>
>       call fixfornam
> RUNSQLSTM command failed.
> SQL9010 received by FIXFORNAM at 400. (C D I R)
> C
> Function check. SQL9010 unmonitored by FIXFORNAM at statement 400,
>   instruction X'000C'.
>
>      Does anyone know what this means?  The message text is useless to me.
>
> Thanks.
>
> Rich
>
>
>
>
>
> ---------------------------------
> Do You Yahoo!?
> Send your FREE holiday greetings online at Yahoo! Greetings.
> _______________________________________________
> 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 ...

Follow-Ups:
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.