Re: MIGRATE EXEC 5.3.0 to 5.4.0

2008-12-31 Thread Larry J Brown
Thanks Tami, looks like that took care of it.  Apparently I have some 
parts to re-work  for PerfToolKit (I had applied a ptf or 2 to that), but 
MIGRATE ran to successful completion.  I had searched IBMLINK for any hits 
on MIGRATE, but only found a couple that were not relevant.  Thanks again!

Larry J. Brown
Shelter Insurance - Information Services
573-214-6314
ljbr...@shelterinsurance.com


This e-mail is intended only for its addressee and may contain information
that is privileged, confidential, or otherwise protected from disclosure.  If
you have received this communication in error, please notify us immediately by
e-mailing postmas...@shelterinsurance.com; then delete the original message.


MIGRATE EXEC 5.3.0 to 5.4.0

2008-12-30 Thread Larry J Brown
Hello, I'm running MIGRATE ALL 530 from my 2nd level 5.4.0 MAINT ID and 
get :

 VMFMGR1315E The VM MIGL530 table does not contain ERROR disk data for 
product 
5VMRSC30  
VMFMGR1320W Migrate restart file, MIGRATE $RESTART A, has been updated due 
to 
errors. Correct the errors, and restart MIGRATE by reissuing 
the 
same command.  

The message help just tells you to reissue MIGLINK on 1st level, and run 
MIGRATE again from 2nd level.  If it fails again - contact the support 
center.  Before I do that, has anybody seen this before, or have a clue to 
what's missing?  RSCS works fine on 5.3.0, and I don't recall doing 
anything special other than tailoring the config file.  It was an initial 
install, not a migration.

Thanks,

Larry J. Brown
Shelter Insurance - Information Services
573-214-6314
ljbr...@shelterinsurance.com


This e-mail is intended only for its addressee and may contain information
that is privileged, confidential, or otherwise protected from disclosure.  If
you have received this communication in error, please notify us immediately by
e-mailing postmas...@shelterinsurance.com; then delete the original message.


Larry J Brown is out of the office.

2008-07-18 Thread Larry J Brown
I will be out of the office starting  07/18/2008 and will not return until
07/23/2008.

I will respond to your message when I return.  If you need help with CICS
or MQ, please contact Scott Weisskirk at x4271.


This e-mail is intended only for its addressee and may contain information
that is privileged, confidential, or otherwise protected from disclosure.  If
you have received this communication in error, please notify us immediately by
e-mailing [EMAIL PROTECTED]; then delete the original message.


Re: Operator Terminal and the Programmable Operator Facility

2008-06-02 Thread Larry J Brown
I have OPERATOR coming up as the default sysoper at IPL and leave it 
logged on to the console.   OP1 and LGLOPR get autologged by AUTOLOG2. 
LGLOPR's PROFILE EXEC sets SYSOPER to himself and invokes PROP using OP1 
as the logical operator, and OP1 has OPERATOR defined as his secondary 
userid.  So non filtered msgs get sent to OP1 which in turn get displayed 
to OPERATOR.  I tried that using OPERATOR as LGLOPR's logical operator, 
but got some weird results with that set up, so got the LGLOPR - OP1 - 
OPERATOR sequence to do what I wanted - not having OPERATOR invoke PROP 
and disc, requiring somebody to manually logon to another ID at the system 
console.  Probably a cleaner way to do, but it works for me - so far.

Thanks,

Larry J. Brown
Shelter Insurance - Information Services
573-214-6314
[EMAIL PROTECTED]



Howard Rifkind [EMAIL PROTECTED] 
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
06/02/2008 02:32 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Operator Terminal and the Programmable Operator Facility






Using the POF (programmable operatior facility) I would like to user the 
same terminal address as the one the Operator came up on when the system 
was IPL'ed.
 
I know I can do a CP disconnect after the Operator does a PROPST and then 
log on the OP1 user to the same terminal address as the Operator was using 
and be able to received messages from the disconnected Operator running 
PROP and send command to the Operator via OP1.  This currently works and 
isn't a problem as the Operator person is doing the CP Disc and then 
logging OP1.
 
The issue for me is that the operations management does not want the 
operator person to have any interaction with the physical terminal during 
this procedure.  So, I have to automate the process and I need some 
suggestions as how to do this.
 
The Operator user id has to start PROP and some how run disconnected.
 
I have to logon OP1 on the same termial to act as the Operator with human 
interaction.
 
I looks easy enough at first but I can't figure out a reasonable way to do 
this.
 
Running z/VM 5.3.  Any suggestions will be appreciated.
 
Thanks



_
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.




This e-mail is intended only for its addressee and may contain information
that is privileged, confidential, or otherwise protected from disclosure.  If
you have received this communication in error, please notify us immediately by
e-mailing [EMAIL PROTECTED]; then delete the original message.


Larry J Brown is out of the office.

2008-05-08 Thread Larry J Brown
I will be out of the office starting  05/08/2008 and will not return until
05/12/2008.

I will respond to your message when I return.


This e-mail is intended only for its addressee and may contain information
that is privileged, confidential, or otherwise protected from disclosure.  If
you have received this communication in error, please notify us immediately by
e-mailing [EMAIL PROTECTED]; then delete the original message.