Re: DFHSM QUESTION - SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL))
Since we have dueling hypothesis, I decided to retest mine against my current level of software. With all my ML2 volumes Delvol'd to Markfull, I then issued a Migrate to ML2. Instead of the expected mount for an existing ML2, HSM mounted a scratch and added a ML2 tape. C'est le vie. We are currently at Z\os 1.9. Willie, What level of Z\os are you running? At 1.4 the outsourcer I was working with at the time complained whenever someone issued a HMIG / ML2 because HSM issued mounts for an existing Primary/Alternate tapes. Of course the Alternate was off-site, hence the complaint. They had Partialtape Markfull as well. From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Douglas Shupe [dsh...@bellsouth.net] Sent: Friday, December 26, 2008 12:17 AM To: IBM-MAIN@bama.ua.edu Subject: Re: DFHSM QUESTION - SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL)) Most likely you have sent a tape that has not been 'marked full' offsite. A list of your ML2 tapes should confirm this. You might consider checking the backup tapes also. - Original Message - From: O'Brien, David W. (NIH/CIT) [C] obrie...@mail.nih.gov Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@bama.ua.edu Sent: Wednesday, December 24, 2008 9:14 AM Subject: Re: DFHSM QUESTION - SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL)) Willie, I was hoping someone would answer citing documentation. If they have, I haven't seen it. Short answer is HSM mounts the last ML2 tape used to satisfy a HMIG / ML2 request. Since you have Duplex = Y for your migrate tapes HSM also wants to mount the alternate. Instruct your operators to reply N to the inevitable Can this tape be mounted msg. HSM will then migrate the dataset and initiate a Tapecopy of the ML2 tape when the migrate is done. Perhaps someone on the list can suggest a way to prevent the average user from migrating datasets to ML2? From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of willie bunter [williebun...@yahoo.com] Sent: Tuesday, December 23, 2008 10:07 AM To: IBM-MAIN@bama.ua.edu Subject: DFHSM QUESTION - SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL)) Good Day To All, I have this parm coded in the DFHSM STC: SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL)) This partion has DUPLEX option: SETSYS DUPLEX(MIGRATION(Y) BACKUP(N) However, for some reason when a user issues a MIGRAT 2 command DFHSM issues a tape mount request for both copies. The problem is that one copy is offsite. Is there a reason why this is occurring? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Computer History Museum
I could sure use a copy of that BPS Loader source code, if anyone has it and is willing to share.. TIA --- Anne Lynn Wheeler wrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. rfocht...@ync.net (Rick Fochtman) writes: I don't remember all the mods we made at NCSS, but one change that made a BIG difference on the simplex and duplex 360/67's was this: in the CP kernel, ALL SVC instructions were modified to a BAL to a specific address in the first 4K of storage, where a vector table rerouted the call to a specific CP subroutine. All those interrupts and PSW swaps took FOREVER on the 360/67, whereas a BAL to low storage SEEMED to fly almost instantaineously. The change also seemed to be beneficial when we switched to 370/168 platforms as well. The CMS kernel used a HVC (in actual fact, a DIAGNOSE) to request services from the CP kernel, including I/O services. We also modified MVT to run in a virtual machine using DIAGNOSE, rather than SIO/TIO/HIO, for I/O services. Made MVT run MUCH FASTER in the virtual machine and freed us from all the related emulation of these I/O instructions. One thing I miss: Grant wrote a program, called IMAGE, that created a complete image of the CP kernel, which would load in record time when bringing up the system. I wish I had a copy of that program now, because of its rather unique processing of the RLD data from the object code. I've never quite understood how RLD data is processed by either the linkage editor or the loader. :-( re: http://www.garlic.com/~lynn/2008s.html#51 Computer History Museum http://www.garlic.com/~lynn/2008s.html#52 Computer History Museum http://www.garlic.com/~lynn/2008s.html#54 Computer History Museum as an undergraduate ... before joining the science center ... I first looked at the standard SVC linkage routine (for all kernel calls) and cut the pathlength by about 75%. I then looked at the most frequently called subroutines ... and changed them to BALRs ... leaving the remaining as SVC ... since it no longer represented a significant portion of CP overhead i.e. while SVC/LPSW was expensive with regard to BALR ... the actual time spent in the original SVC linkagereturn was much, much larger than the SVC/LPSW instruction ... most of the benefit came from reducing the logic. The next was the BALR ... not only replaced the SVC/LPSW instructions but were also eliminated the rest of the logic for the linkage/return for high-use routines. When that was done, the remaining SVC/LPSW (and associated linkage/return overhead) was a trivial percentage of overall time spent in the kernel. Remaining big overhead wasn't so much the SIO instruction ... but the channel program simulation overhead done in CCWTRANS. CMS turned out to do very stylized disk channel programs. I created a fastpath channel program emulation operation for CMS disk I/O (that was also syncronous ... avoiding all the virtual machine gorp for entering wait state, asyncronous interrupts, etc). This got severely criticized by the people at the science center (mostly bob adair) because it violated the 360 principles of operation. However, it did significantly reduce cp67 kernel overhead for operating CMS virtual machines. This was then redone using DIAGNOSE instruction ... since the 360 principles of operation defines the DIAGNOSE instruction operation as model-dependent. The facade was that there was a 360 virtual machine machine model which had its own definition for DIAGNOSE instruction operation. Standard CP67 saved core image of the loaded kernel to disk (routine SAVECP) and a very fast loader sequence that brought back that image back into memory on IPL and then transferred to CP67 startup routine CPINIT. One of the people at the science center modified CP67 kernel failure processing to write a image dump to disk area and then simulate reloaded the disk kernel image from scratch ... basically automagically failure/restart ... this is mentioned in one of the referenced stories at MULTICS websites ... one of the people who supported CP67 system at MIT (and later worked on MULTICS) had modified TTY/ASCII terminal line processing that would cause the system to crash ... and one day CP67 crashed and automagically (fast) restarted 27 times in a single day (which help instigate some MULTICS rewrite because it was taking an hour elapsed time to restart). The cp67 kernel was undergoing was amount of evolution with new functions being added. On 768k real storage machine ... every little bit hurt. So I did a little slight of hand and created a virtual address space that mapped the cp67 kernel image ... and then flagged the standard portion as fixed ... but created an infrastructure that allowed other portions to be paged in out. This required enhancing the SVC linkage infrastructure to recognize portions of the
Re: DFHSM QUESTION - SETSYS PARTIALTAPE(MIGRATION(MARKFULL) BACKUP(MARKFULL))
At one site, we put a process in place to run a LIST TTOC looking for partials, generating and running the DELVOL MARKFULL commands before the alternates were taken offsite. The main culprit in this case was that command level backup (i.e. HBACKDS) does not use the PARTIALTAPE parm for backup; this is only used for automatic backup process or a BACKVOL command, I believe. Using INUSE(RETRY) can also cause this issue, since the backup retries are queued as command level backups. I do not recall if (or how) ML2 tapes were affected. An alternative might be to use the ARCMDEXT exit and check if Interval Migration or PSM is in progress. If the answer to both is no, then I think it would be a command level migration of some kind and the output could be directed to DASD rather than TAPE. You would need to set a RC=36 or 40 in the exit, depending on whether you want the dataset to be compacted on DASD or not. More information on the ARCMDEXT can be found at: http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/DGT2C760/6.10? SHELF=EZ2ZO10LDT=20080603102513 Hope this helps in some way. Chris Taylor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a new group
for anyone who is listed under the NTBL NAME(SYSPRGSX). There is only one
entry in NTBLENT. This was done in order for various people to do the SDSF LOG
command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be appreciated.
Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
ISYS(LOCAL),/* Initial system default for DA */
LANG(ENGLISH), /* Default language*/
LOGOPT(OPERACT),/* Default log option */
OWNER(NONE),/* Default owner */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB), /* Valid character translate table */
VIO(SYSALLDA) /* Unit name for page mode output */
//
/* Sample NTBL list */
//
NTBL NAME(SLIST)
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7)
NTBLENT STRING(PAY),OFFSET(3)
NTBL NAME(SYSPRGSX)
NTBLENT STRING(E18823),OFFSET(1)
_
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.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SDSF Question
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe. Also, It would
probably help to add this to the paragraph:
IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT. This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be
appreciated. Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
ISYS(LOCAL),/* Initial system default for DA */
LANG(ENGLISH), /* Default language*/
LOGOPT(OPERACT),/* Default log option */
OWNER(NONE),/* Default owner */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB), /* Valid character translate table */
VIO(SYSALLDA) /* Unit name for page mode output */
//
/* Sample NTBL list */
//
NTBL NAME(SLIST)
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7)
NTBLENT STRING(PAY),OFFSET(3)
NTBL NAME(SYSPRGSX)
NTBLENT STRING(E18823),OFFSET(1)
_
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.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail
Re: SDSF Question
Just reread your post, you do have the IUID parm(didn't see it). I
don't see a name however NAME(SYSPRGSX). Not sure if that is a problem
or not. My guess is your new GROUP is AFTER the the one you already
had, and the selection on that one is a first match.
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: Jousma, David
Sent: Friday, December 26, 2008 3:25 PM
To: 'IBM Mainframe Discussion List'
Subject: RE: SDSF Question
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe. Also, It would
probably help to add this to the paragraph:
IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT. This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be
appreciated. Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
ISYS(LOCAL),/* Initial system default for DA */
LANG(ENGLISH), /* Default language*/
LOGOPT(OPERACT),/* Default log option */
OWNER(NONE),/* Default owner */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB), /* Valid character translate table */
VIO(SYSALLDA) /* Unit name for page mode output */
//
/* Sample NTBL list */
//
NTBL NAME(SLIST)
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7)
NTBLENT STRING(PAY),OFFSET(3)
NTBL NAME(SYSPRGSX)
NTBLENT STRING(E18823),OFFSET(1)
_
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure,
Re: SDSF Question
Thanks David,
The problem is that when user E18823 logs into SDSF with the LOG command SDSF
isn't setting the log column location to column 51.
Jousma, David david.jou...@53.com 12/26/2008 3:24 PM
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe. Also, It would
probably help to add this to the paragraph:
IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT. This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be
appreciated. Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
ISYS(LOCAL),/* Initial system default for DA */
LANG(ENGLISH), /* Default language*/
LOGOPT(OPERACT),/* Default log option */
OWNER(NONE),/* Default owner */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB), /* Valid character translate table */
VIO(SYSALLDA) /* Unit name for page mode output */
//
/* Sample NTBL list */
//
NTBL NAME(SLIST)
NTBLENT STRING($S),OFFSET(1)
NTBLENT STRING(P),OFFSET(7)
NTBLENT STRING(PAY),OFFSET(3)
NTBL NAME(SYSPRGSX)
NTBLENT STRING(E18823),OFFSET(1)
_
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.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at
Re: SDSF Question
When the user logs on, have them issue who on the command line. It
will give you a wealth of info, so that you know they are being
correctly selected and assigned the group you intend.
I also read this in the SDSF book about ILOGCOL:
This parameter is ignored if the screen on which the SYSLOG or OPERLOG
is displayed can display the entire width of the SYSLOG/OPERLOG. Also,
if the value for position-number is so high that less than a full screen
of data is displayed on the SYSLOG or OPERLOG panel, SDSF adjusts the
starting position number to display a full screen of data. For example,
if the width of the screen on which the SYSLOG is displayed is 80
characters, SDSF adjusts the value of position-number to ensure that 80
characters of data are displayed
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:35 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SDSF Question
Thanks David,
The problem is that when user E18823 logs into SDSF with the LOG command
SDSF isn't setting the log column location to column 51.
Jousma, David david.jou...@53.com 12/26/2008 3:24 PM
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe. Also, It would
probably help to add this to the paragraph:
IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT. This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be
appreciated. Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
ISYS(LOCAL),/* Initial system default for DA */
LANG(ENGLISH), /* Default language*/
LOGOPT(OPERACT),/* Default log option */
OWNER(NONE),/* Default owner */
UPCTAB(TRTAB2), /* Upper case translate table name */
VALTAB(TRTAB), /* Valid character translate table */
VIO(SYSALLDA) /* Unit name for page mode output */
Re: SDSF Question
Please bare with me a moment and let me redefine what I'm after:
I have two groups, both of which start with:
GROUP NAME(ISFSPROG),
TSOAUTH(JCL,OPER,ACCT),
and the second:
GROUP NAME(SYSPRGSX),
TSOAUTH(JCL,OPER,ACCT),
I want the people who have the TSOAUTH... of the second group to have their
SDSF/LOG command start them at column #51
ILOGCOL(51),
How can I do this. Right now as things stand all are falling into the first
group.
Thanks
Jousma, David david.jou...@53.com 12/26/2008 3:48 PM
When the user logs on, have them issue who on the command line. It
will give you a wealth of info, so that you know they are being
correctly selected and assigned the group you intend.
I also read this in the SDSF book about ILOGCOL:
This parameter is ignored if the screen on which the SYSLOG or OPERLOG
is displayed can display the entire width of the SYSLOG/OPERLOG. Also,
if the value for position-number is so high that less than a full screen
of data is displayed on the SYSLOG or OPERLOG panel, SDSF adjusts the
starting position number to display a full screen of data. For example,
if the width of the screen on which the SYSLOG is displayed is 80
characters, SDSF adjusts the value of position-number to ensure that 80
characters of data are displayed
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:35 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SDSF Question
Thanks David,
The problem is that when user E18823 logs into SDSF with the LOG command
SDSF isn't setting the log column location to column 51.
Jousma, David david.jou...@53.com 12/26/2008 3:24 PM
You don't say what the actual problem is, but remember, when using
ISFPARM's like this, the match is top down I believe. Also, It would
probably help to add this to the paragraph:
IUID(SYSPRGSX), /* NAME TABLE USED FOR SELECTION
*/
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Howard Rifkind
Sent: Friday, December 26, 2008 3:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: SDSF Question
Hello all,
Below is an entry I placed is the ISFPARM's file in order to create a
new group for anyone who is listed under the NTBL NAME(SYSPRGSX).
There is only one entry in NTBLENT. This was done in order for various
people to do the SDSF LOG command and have the log come up at column 51.
I executed the following without any errors:
F SDSF,REFRESH,M(HR)
ISF304I Modify REFRESH command accepted.
ISF726I SDSF parameter processing started.
ISF739I SDSF parameters being read from member ISFPRMHR of data set
SYS2.PARMLIB.
ISF728I SDSF parameters have been activated.
However this isn't working. What am I missing? Any help would be
appreciated. Thanks.
GROUP IUID(SYSPRGSX), /* Group name */
TSOAUTH(JCL,OPER,ACCT), /* User must have JCL, OPER, ACCT */
ACTION(ALL),/* All route codes displayed */
ACTIONBAR(YES), /* Display the action bar on panels*/
APPC(ON), /* Include APPC sysout */
AUPDT(2), /* Minimum auto update interval*/
AUTH(LOG,I,O,H,DA,DEST,PREF, /* Authorized functions */
SYSID,ABEND,ACTION,INPUT,
FINDLIM,ST,INIT,PR,TRACE,
ULOG,MAS,SYSNAME,LI,SO,NO,PUN,RDR,JC,SE,RES),
CMDAUTH(ALL), /* Commands allowed for all jobs */
CMDLEV(7), /* Authorized command level*/
CONFIRM(ON),/* Enable cancel confirmation */
CURSOR(ON), /* Leave cursor on last row processed */
DADFLT(IN,OUT,TRANS,STC,TSU,JOB), /* Default rows shown on DA */
DATE(MMDD), /* Default date format */
DATESEP('/'), /* Default datesep format */
DFIELD2(DAFLD2),/* Sample alternate field list for DA */
DISPLAY(OFF), /* Do not display current values */
DSPAUTH(ALL), /* Browse allowed for all jobs */
GPLEN(2), /* Group prefix length */
ILOGCOL(51),/* Initial display column in log */
Re: Computer History Museum
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. rfocht...@ync.net (Rick Fochtman) writes: I could sure use a copy of that BPS Loader source code, if anyone has it and is willing to share.. re: http://www.garlic.com/~lynn/2008s.html#51 Computer History Museum http://www.garlic.com/~lynn/2008s.html#52 Computer History Museum http://www.garlic.com/~lynn/2008s.html#54 Computer History Museum http://www.garlic.com/~lynn/2008s.html#56 Computer History Museum the vm370 loader source (both dmkldr00e and dmsldr) have genesis from similar origins. here is reference to hercules vm370 release 6 (that has source): http://osdir.com/ml/emulators.hercules390.vm/2004-06/msg00018.html the mentioned cp67 pageable kernel modifications weren't picked up and shiped as part of cp67 product ... but something similar did appear with vm370 product. the hercules reference (CMS) DMSLDR (in release 6) having 255 externals per TEXT file ... while the original BPS loader had limitation of a total of 255 external symbols. reference for vm/370 R6 (including base source): http://www.cbttape.org/vm6.htm the above has reference to aws file (which is over 4mbytes, compress, over 32mbytes uncompressed) http://www.cbttape.org/ftp/vm6/base-source.aws.bz2 reference to awstape utility: http://www.cbttape.org/awstape.htm -- 40+yrs virtualization experience (since Jan68), online at home since Mar70 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Attachmate Extra! Toolbar editor - Usage assistance
Is there someone familiar with the idiosyncrasies of the Attachmate Extra! toolbar editor. I am working with version 6.71. The editor does not seem to work as stated when I attempt to work with many of the toolbars I've tried to modify or create. Specifically, if I want to move a button around it simply does not move to where I move it too. Most of the time is jumps back to where it started or other times overlays another button. The HELP seems of no assistance as it simply says to move the buttons where you would like using the mouse and let it go where you like. Also... on changing the size of a button, HELP states to do this using the corner connectors and the mouse but this does nothing. I'm assuming the editor has some issues so I was hoping someone out there had some inside tricks or work arounds in working with this toolbar editor. FYI - I've scowered Attachmate's Support site but to no avail. Thanks --- Bill George __ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Computer History Museum
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. rfocht...@ync.net (Rick Fochtman) writes: I could sure use a copy of that BPS Loader source code, if anyone has it and is willing to share.. re: http://www.garlic.com/~lynn/2008s.html#64 Computer History Museum double checking, the vm370 R6 base-source.aws file contains both (CMS) DMSLDR ASSEMBLE and (CP) DMKLD00E ASSEMBLE files. DMKLD00E ASSEMBLE would be the closest to the original BPS loader source. -- 40+yrs virtualization experience (since Jan68), online at home since Mar70 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SDSF Question
SDSF scans ISFPARMS from the beginning and assigns users to the first group for which they are qualified. This means that the order of the group definitions is important: Arrange them from most selective to least selective. Don Imbriale -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Howard Rifkind Sent: Friday, December 26, 2008 5:16 PM To: IBM-MAIN@bama.ua.edu Subject: Re: SDSF Question Please bare with me a moment and let me redefine what I'm after: I have two groups, both of which start with: GROUP NAME(ISFSPROG), TSOAUTH(JCL,OPER,ACCT), and the second: GROUP NAME(SYSPRGSX), TSOAUTH(JCL,OPER,ACCT), I want the people who have the TSOAUTH... of the second group to have their SDSF/LOG command start them at column #51 ILOGCOL(51), How can I do this. Right now as things stand all are falling into the first group. Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: GDPS Implementation CPU Requirement
As has been already pointed out, usage during normal processing is minimal, but perhaps the most critical sizing point is the cycles used during a freeze. Insufficient weighting given to the K LPAR (and/or the ANTMAIN/ANTAS* tasks set too low) may elongate the freeze time. This would be rather important (unless you are doing freeze and stop) as all volumes are locked out until the suspends are issued and the long busy is released. Usage will be based on number of LCUs and devices but should be tested and measured. Best regards, John On Tue, 23 Dec 2008 20:07:38 +0100, John Ticic IBM-MAIN ibm- ma...@sysprog-edv.de wrote: Bob's estimate sounds about right. The control LPARs don't burn many CPU cycles. There will be a peak (or multiple peaks - depending) during the day when the status of the DASD is checked. Depending on how many devices you have, it is probably a good idea to plan this task for a quiet time. I really can't remember the numbers, but it was noticeable. Getting technical information is a little bit difficult. Once you've signed up with IBM for GDPS, you can get the technical documentation, and there is a lot of good stuff in there. You can probably tap into some good user information at Share (or visit the Web site and look for presentations). Regards John -- cut -- Based on previous experience I had with a z9 EC one-way and a two-way, about 10-15% of one CP on average. YMMV If by cost you mean MSUs, that also was minimal. I seem to remember 5-8 MSUs being consumed. Again, YMMV according to how your shop has negotiated your software licenses. Bob -Original Message- Does anybody know what are the CPU cost to implement GDPS (for the control LPARs)? How much CPU usage we should expect on top of our existing CPU usage? This is assuming we already have both parallel sysplex implemented in both primary and secondary site in place. What other cost/overhead we should expect aside from higher CPU and CF usage? Any good reference material? TIA. Regards, Jason John Ticic IntelliMagic - Storage Intelligence Perzikweg 13a, 2321 DG Leiden, The Netherlands www.intellimagic.net -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Computer History Museum
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. re: http://www.garlic.com/~lynn/2008s.html#51 Computer History Museum http://www.garlic.com/~lynn/2008s.html#52 Computer History Museum http://www.garlic.com/~lynn/2008s.html#54 Computer History Museum http://www.garlic.com/~lynn/2008s.html#56 Computer History Museum http://www.garlic.com/~lynn/2008s.html#64 Computer History Museum http://www.garlic.com/~lynn/2008s.html#65 Computer History Museum for additional topic drift, mention of NCSS ( nomad) in an old baybunch announcement: http://www.garlic.com/~lynn/2007c.html#email830711b in this post http://www.garlic.com/~lynn/2007c.html#12 the post includes a number of old email ... including discussion of highly modified internal vm370 distribution http://www.garlic.com/~lynn/2007c.html#email830705 and http://www.garlic.com/~lynn/2007c.html#email830709 and http://www.garlic.com/~lynn/2007c.html#email830711 -- 40+yrs virtualization experience (since Jan68), online at home since Mar70 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
