Hello,
If you use rexec from two Linux, looks like the Linux side are ok.
>From the MVS side, I used this Job to test this kind of work, but my test
was from to send a command (NETSTAT in this test) from MVS to VM (OP1
machine).
Nothing needed at MVS side.
Adjust for your environment and test it:
This is how I do it - highly recommend using SSH instead of R-anything. Makes
your security auditors happy.
//SFTPPRF1 EXEC PGM=BPXBATCH,PARM=('SH ssh -o $O1 -l $L $S $CMD')
//STDOUT DD SYSOUT=(,)
//STDERR DD SYSOUT=(,)
On Oct 9, 2009, at 10:34 AM, Jones, Russell wrote:
Does anyone have any experience running remote linux commands from
MVS batch? I have found that MVS TSO has REXEC and RSH, but I am
been unsuccessful executing a remote command on linux. I can use
rexec/rsh from one linux system to another, but
Does anyone have any experience running remote linux commands from MVS batch? I
have found that MVS TSO has REXEC and RSH, but I am been unsuccessful executing
a remote command on linux. I can use rexec/rsh from one linux system to
another, but not from MVS.
Any help on using these commands, o
Some examples from other OS implementations, which show (even within a
vendor) differing results. Is AIX right or is SLES 10 right? I'm not
sure.
SuSE (or probably the level of Korn Shell) changed (I think) between
SLES 9 and SLES 10. AIX and Solaris seem to be acting "as a human
expects."
---
>>> On 10/9/2009 at 9:38 AM, Neale Ferguson wrote:
> 0605 as an octal number is 389. So 389/100 = 3 when truncated.
And just to be explicit about _why_ it's being interpreted as an octal number,
it's because of the leading zero.
Mark Post
0605 as an octal number is 389. So 389/100 = 3 when truncated.
On 10/9/09 9:30 AM, "Scully, William P" wrote:
> I've reported this to the vendor but I found this error a bit
> astonishing:
>
> # ksh -vx poo.ksh
> date=0605
> + date=0605
> ((mm=${date}/100))
> + ((mm=0605/100))
> echo ${mm}
> +
I've reported this to the vendor but I found this error a bit
astonishing:
# ksh -vx poo.ksh
date=0605
+ date=0605
((mm=${date}/100))
+ ((mm=0605/100))
echo ${mm}
+ echo 3
3
exit 0
+ exit 0
I get this result on SLES 10.
--
For
You need to restore the share segment from the old system to the new. The
spxtape command will backup and restore DCSS and save system. Question, on your
IPL volume, do you have spool space allocated. In the old days I use to have
two vm sysyem to manage. This was one of things I need to do when
Brad Hinson wrote:
>This is just the new format for output from lsdasd. It is now
>PAV-aware, so it knows that (in this example) disks 206 and 207 are
>aliases. You can still use these devices (base+alias) in a multipath,
>using the device-mapper-multipath package. As a reminder, for RHEL this
>
> For example I managed to get it up boot but I couldn't get CMS to start:
>
> 03:14:54 ipl 190
> DMSWSP327I The installation saved segment could not be loaded
> z/VM V5.4.02008-10-13 07:27
>
> DMSDCS1083E Saved segment CMSPIPES does not exist
> DMSDCS1083E Saved segment CMSPIPES does not
Lee,
Maybe a stupid question, but have you compared the minidisk definitions on
both Linuxes and checked if all the different layers say R/W ?
>From each Linux:
# vmcp q v
# vmcp q md location
# cat cat /sys/devices/css*/*/0.0./readonly
Also, I hope your planning to use a shared directory and
On Fri, Oct 9, 2009 at 10:17 AM, Chan Kok Leong wrote:
> For example I managed to get it up boot but I couldn't get CMS to start:
>
> 03:14:54 ipl 190
> DMSWSP327I The installation saved segment could not be loaded
> z/VM V5.4.0 2008-10-13 07:27
>
> DMSDCS1083E Saved segment CMSPIPES does
Yes, I had tried following the procedure described in the pdf but it does seems
incomplete (deliberate?).
For example I managed to get it up boot but I couldn't get CMS to start:
03:14:54 ipl 190
DMSWSP327I The installation saved segment could not be loaded
z/VM V5.4.02008-10-13 07:27
14 matches
Mail list logo
