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


  1.  Home
  2. MIDRANGE-L
  3. June 2014

Re: MIDRANGE-L Digest, Vol 13, Issue 981

That is as low as we can go. What time can we expect you tomorrow?

Terry
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: midrange-l-request@xxxxxxxxxxxx
Sender: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>Date: Thu, 19 Jun 2014 08:01:22
To: <midrange-l@xxxxxxxxxxxx>
Reply-To: midrange-l@xxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 13, Issue 981

Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MIDRANGE-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. RE: QSYSOPR Security issue for Backups. (Steinmetz, Paul)
2. feedback from a unix command run from CL (Mike Cunningham)
3. Re: feedback from a unix command run from CL (Scott Klement)
4. Re: DSPSIZ issue (Hoteltravelfundotcom)
5. RE: DSPSIZ issue (Scott Mildenberger)
6. Re: DSPSIZ issue (Hoteltravelfundotcom)
7. RE: feedback from a unix command run from CL (Mike Cunningham)
8. Shipping issues (rob@xxxxxxxxx)


----------------------------------------------------------------------

message: 1
date: Wed, 18 Jun 2014 15:07:04 -0400
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: RE: QSYSOPR Security issue for Backups.

I just tested CMD('clrtmp') via QSH
Fails because of an authority issue with QPGMR
QSTRUP runs as QPGMR, so we need determine what authority is needed by QPGMR to clear all the files in tmp.
Because it runs in QSH, not as easy to see the authority issues.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, June 18, 2014 1:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: QSYSOPR Security issue for Backups.

Paul & Rob,

clrtmp is a QShell command. You should not run QShell tools with the CALL command or a *CMD object. These tools are meant to run inside QShell, and could potentially need the services of the shell to work properly.

So while calling it from the CL environment may wotk today, it has the potential to break at any time when you update the software. And there may be things that 'seem' to work, but don't really work under the covers.

So, please consider running this from QShell as it is meant to run.

QSH CMD('clrtmp')


On 6/18/2014 12:04 PM, rob@xxxxxxxxx wrote:
If you want a command, it's really quite simple.
EDTF FILE(ROUTINES/QCMDSRC) MBR(DUMMY)
..+....2....+....3....+....4....+....5....+.
************Beginning of data************** CMD PROMPT('Dummy source
no parm commands')
************End of Data********************

CRTCMD CMD(QGPL/CLRTMP) PGM(QSHELL/CLRTMP)
SRCFILE(ROUTINES/QCMDSRC) SRCMBR(DUMMY)


Rob Berendt


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



------------------------------

message: 2
date: Wed, 18 Jun 2014 19:39:46 +0000
from: Mike Cunningham <mike.cunningham@xxxxxxx>
subject: feedback from a unix command run from CL

Is there a way to detect the results of a unix shell command run from a CLLE program?

I want to run the cmp qshell command from CL against two IFS files.
Cmp returns and Exit Status
0 when the files are identical
1 when the files are different
1 when an error occurred
I want to take additional action in the CL if the exit status is 1

Mike Cunningham


------------------------------

message: 3
date: Wed, 18 Jun 2014 14:50:31 -0500
from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
subject: Re: feedback from a unix command run from CL

When the STRQSH command is finished, it should send you a QSH0005
completion message containing the exit status.

You should be able to receive that message... the exit status should be
a binary value in the first 4 bytes of the msgdta.


On 6/18/2014 2:39 PM, Mike Cunningham wrote:
Is there a way to detect the results of a unix shell command run from a CLLE program?

I want to run the cmp qshell command from CL against two IFS files.
Cmp returns and Exit Status
0 when the files are identical
1 when the files are different
>1 when an error occurred
I want to take additional action in the CL if the exit status is 1

Mike Cunningham



------------------------------

message: 4
date: Wed, 18 Jun 2014 17:52:58 -0400
from: Hoteltravelfundotcom <hoteltravelfun@xxxxxxxxx>
subject: Re: DSPSIZ issue

I am using Iseries access for windows. where do i make this change to this
setting?


On Tue, Jun 17, 2014 at 6:03 AM, Winchester Terry <
terry.winchester@xxxxxxxxxxxxxxx> wrote:


If your running Client Access your either set up for 24x80 or 27x132
screen sizes. Here's a link to calling the QsnQryModSup API of the
Display Station Manager from a CL program to inquire the display
station mode:

http://archive.midrange.com/midrange-l/201101/msg00463.html

In general, declaring DSPSIZ(27 132) in your display file creates
this message when the workstation is only setup for 24x80.

Terry

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of Hoteltravelfundotcom
Sent: Monday, June 16, 2014 6:06 PM
To: Midrange Systems Technical Discussion
Subject: DSPSIZ issue

AM getting this message when running a CL that displays data. How do I
determine what the correct
DSPSIZ should be?

Message ID . . . . . . . . . :
CPF4169
Message file . . . . . . . . :
QCPFMSG
Library . . . . . . . . . :
QSYS


Message . . . . : The device file does not contain an
entry for screen
size.
Cause . . . . . : The file &2 in library &3 display size (DSPSIZ)
parameter
value is not the screen size of the device
&4.
Recovery . . . : Close the file. Change the DSPSIZ parameter
value.
Create the file again, and then try the command
again.
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected by
applicable legal privileges, or constitute non-public information. It is
intended to be conveyed only to the designated recipient(s). If you are not
an intended recipient of this message, please notify the sender by replying
to this message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




------------------------------

message: 5
date: Wed, 18 Jun 2014 22:08:35 +0000
from: Scott Mildenberger <SMildenberger@xxxxxxxxxxxxxxxxxx>
subject: RE: DSPSIZ issue

On the menu at the top: Communication->Configure. The size setting is about half way down.

Scott

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hoteltravelfundotcom
Sent: Wednesday, June 18, 2014 3:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: DSPSIZ issue

I am using Iseries access for windows. where do i make this change to this setting?



------------------------------

message: 6
date: Wed, 18 Jun 2014 18:08:55 -0400
from: Hoteltravelfundotcom <hoteltravelfun@xxxxxxxxx>
subject: Re: DSPSIZ issue

soorry never mind i got it.


On Wed, Jun 18, 2014 at 5:52 PM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:

I am using Iseries access for windows. where do i make this change to this
setting?


On Tue, Jun 17, 2014 at 6:03 AM, Winchester Terry <
terry.winchester@xxxxxxxxxxxxxxx> wrote:


If your running Client Access your either set up for 24x80 or 27x132
screen sizes. Here's a link to calling the QsnQryModSup API of the
Display Station Manager from a CL program to inquire the display
station mode:

http://archive.midrange.com/midrange-l/201101/msg00463.html

In general, declaring DSPSIZ(27 132) in your display file creates
this message when the workstation is only setup for 24x80.

Terry

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of Hoteltravelfundotcom
Sent: Monday, June 16, 2014 6:06 PM
To: Midrange Systems Technical Discussion
Subject: DSPSIZ issue

AM getting this message when running a CL that displays data. How do I
determine what the correct
DSPSIZ should be?

Message ID . . . . . . . . . :
CPF4169
Message file . . . . . . . . :
QCPFMSG
Library . . . . . . . . . :
QSYS


Message . . . . : The device file does not contain an
entry for screen
size.
Cause . . . . . : The file &2 in library &3 display size (DSPSIZ)
parameter
value is not the screen size of the device
&4.
Recovery . . . : Close the file. Change the DSPSIZ parameter
value.
Create the file again, and then try the command
again.
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected by
applicable legal privileges, or constitute non-public information. It is
intended to be conveyed only to the designated recipient(s). If you are not
an intended recipient of this message, please notify the sender by replying
to this message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





------------------------------

message: 7
date: Thu, 19 Jun 2014 12:49:42 +0000
from: Mike Cunningham <mike.cunningham@xxxxxxx>
subject: RE: feedback from a unix command run from CL

Thanks Scott. This helped me find everything I needed and I have it working. I do notice that every qshell command I run creates two additional joblogs with user data QZSHSH and QP0ZSPWP. Is there ever anything in these joblogs that would make it worth keeping for a few days? I found some recommendations on how to stop them from being created (CHGJOB *NOLIST just before the STRQSH) or a DLTSPLF run on a regular basis.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, June 18, 2014 3:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: feedback from a unix command run from CL

When the STRQSH command is finished, it should send you a QSH0005 completion message containing the exit status.

You should be able to receive that message... the exit status should be a binary value in the first 4 bytes of the msgdta.


On 6/18/2014 2:39 PM, Mike Cunningham wrote:
Is there a way to detect the results of a unix shell command run from a CLLE program?

I want to run the cmp qshell command from CL against two IFS files.
Cmp returns and Exit Status
0 when the files are identical
1 when the files are different
>1 when an error occurred
I want to take additional action in the CL if the exit status is 1

Mike Cunningham


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.