Another thing I notice is it appears as though you are running MySQL in
"safe" mode which is not secure nor is it meant for real production.
You don't mention how you put MySQL on the system, but if it's part of the
Zend Server distribution then I strongly suggest you start it there
manually, and if the subsystem is set up properly you would not need to
start MySQL as a Deamon in QUSRSYS, rather it would run in its own
subsystem. That subsystem has the pre/auto start jobs needed to start
Chief Technical Architect
Agile Technology Architects
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark
Sent: Wednesday, June 25, 2014 10:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: problems starting mysql qp2term vs qsh
The STRQSH (or QSH) command invokes the OS/400 QShell ... but that does not
run in PASE, and is not the same as the PASE shell.
You need to CALL QP2SHELL or QP2SHELL2 in order to run that command in a
for a good explanation of the differences.
Hope that helps,
Mark S. Waterbury
On 6/25/2014 10:47 AM, Dale Janus wrote:
We need mysql to run some programs on our internal website. We cannot
get a QSH script to start it automatically, even though it looks
identical to entering the commands in QP2TERM.
The only way we can start MYSQL is to enter these three lines from a
bin/mysqld_safe --user=mysql &
Lately we have been taking down qinter subsystem at night and that
ends mysql since qp2term is tied to an emulation session.
We created a cl command using qsh so we could automate the start up
QSH CMD('cd +
-power-64bit; bin/mysqld_safe --user=mysql &')
This command looks like it works, but our website reports mysql not
running errors:Warning: mysql_connect(): No such file or directory in
/www/mysql.php on line 2 No such file or directory
This automated shut down CL command works:
QSH CMD('cd +
-power-64bit; bin/mysqladmin -u root shutdown')
When we run the qp2term commands, it looks like this:
> cd /QOpenSys/usr/local/mysql/mysql-5.1.39-i5os-power-64bit
> bin/mysqld_safe --user=mysql &
$ 140625 10:02:50 mysqld_safe Logging to
140625 10:02:59 mysqld_safe Starting mysqld daemon with databases
from /QOpen Sys/mysql/data
140625 10:03:40 mysqld_safe mysqld from pid file
When we run the CL program calling QSH it looks like this:
140625 10:04:19 mysqld_safe Logging to
140625 10:04:31 mysqld_safe Starting mysqld daemon with databases
140625 10:04:36 mysqld_safe mysqld from pid file
Press ENTER to end terminal session.
(it does not matter if I press ENTER to end terminal session or not)
even though it looks like the QSH script is working just like the
QP2TERM commands, MYSQL does not work on our web site. Can anyone
explain the difference ?