Yesterday, I found the oeconsol program on the IBM z/OS UNIX tools page at
http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1ty2.html
The source includes the JCL to assemble and link-edit into TSO and USS.
Word of warning, you will get RC=4 from oeconsol if you are in SDSF (in TSO)
at the
Hello IBM-MAIN people,
We recently have installed a new IBM Tape Library (without a VTS) to
replace a very old STK Silo; so we are migrating our tape usage from 3490's to
3590's - about a hundred-fold increase increase in capacity per cartridge (and
will have many fewer cartridges!)! This
I would like to see BatchPipes available in TSO.
When I did VM/CMS work, pipes were the best thing since sliced bread.
The best CMS application was CHARLOTTe - the web browser for 3270
screens in CMS.
--
For IBM-MAIN subscribe
Hello John,
In our TSO signon CLIST (I know it should be Rexx ), at the very end,
after re-allocating libraries (etc.), we use:
/*ALL DONE*/
FREE FI(TEST)
ERROR RETURN
IF SYSLTERM EQ 0 THEN EXIT
ISPSTART PNL NEWAPPL(ISR)
The test on SYSLTERM will EXIT if we are using Telnet (not
If you are processing your SMF data with SAS (e.g. MXG, MICS, RYO, etc.),
just use something like this example (from http://support.sas.com):
Sample 38159: Create XML on z/OS using the XML LIBNAME engine
Creating XML files on z/OS can be accomplished by using the XML LIBNAME
engine. When
Assuming you have enough concurrent work happening (like Ted said about
INITs and max TSO users), I would think about changing SYSA and SYSC to
both use 4 LPs.
With SYSA and SYSC competing for all four processors, SYSB can float around
and use free cycles.
This assumes you do not have a single
I say get the vendors to provide the tools and/or analysis to prove their
claims.
They may ask for SMF data from the existing environment to put through their
modeling tools. Make sure they ask for specific SMF record types, as you do
not want to send huge volumes of SMF data to the vendors.
What about NETTIME used by NTP (and friends).
--
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
Please describe what you have now, and what you want in the future.
Do you have an existing system running in an (at least one) LPAR running z/OS?
If so, build a one-pack (or two-pack) system in your current LPAR (Mark
Zelden's procedures have worked for me), then use HCD to move the pack(s)
to
I'm looking for the control block and field name that contains the name of the
procedure (or the member name of the PROCLIB) used in a step.
I have an assemble program that displays the following for a job step:
JobName, StepName, ProcStep, ProgramName, UserID
And I would really like to round
The things I liked in Xedit include, being able to split the screen vertically
and
more than two screens visible. Being able to change the whole layout of the
screen (do you remember the EDGAR compatiblity exec?) - you have control of
where the prefix area is (left or right; how many
Are you sure your code didn't suffer the same fate as IEFBR14?
The story (Urban Legend?) I heard, was that IEFBR14 was originally just a BR
14, but that code was APAR'd to add a SR 15,15 before the BR 14 to set
the return code to zero. But then along came a problem with the loader, it
seems
Getting back on target
Doesn't anyone remember the Christmas Tree viral worm?
As I recall, it was an e-mail with an attachment; the reader
was instructed to save the attachment as a EXEC, and run
it to see the Christmas greeting. While the greeting was displayed,
the EXEC harvested the
What about writing a small assembler routine to do the AMODE switch.
The routine would use an input value of say -1 for query, 0 for set to 24-
bit mode, 1 for set to 31-bit mode, and by extention, 2 to set to 64-bit
mode. The routine would return (either as a function call, or in a separate
Here try something like this:
//SY32927P JOB (ACCTNUM,EXP),'CICS/TS31 TABLEASM',
// NOTIFY=SYSUID,
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
//*
//PROCLIB JCLLIB ORDER=SYS1.CICSTS31.PROCLIB
//*
// EXEC DFHAUPLE,INDEX2='CICSTS31.CICS',NAME='SDFHAUTH'
//*
//ASSEM.SYSUT1 DD DISP=SHR,
//
What are the normal USS permission bits for the directory? Checking the
permission bits should be done before ACF2 is called to check rules.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
As I said to the pervious version of this question: Check the permission bits
on
the directory. The system should check the permission bits before calling ACF2
to check the rules.
Checking the mount attributes for R/W should also be done.
You try the following:
Trap the error for over-flowing the AIX key (with low values), and re-try the
insert/update after incrementing the right most byte (or 2, or 4 bytes) of the
alternate key to create a new key.
--
For
I think the key is the VTAM construct IUTSAMEH - this is used in Enterprise
Extender (EE). You need a HOME IP address for VTAM to use, different from
TCPIP's HOME IP address. It is defined in the VTAMLST(ACTSTRxx), as
IPADDR=xxx.xxx.xxx.xxx (dotted IP number address) along with NODETYPE=NN.
Since you are using Client FTP in TSO, you need the TSO MOUNT privilege and
you need AUTOTAPEMOUNT specified in your FTP.DATA file. There are several
places where the FTP.DATA file can be found, make sure you get the correct
one.
IBM still supports the 3270 family of products in software (including OS's,
CICS, TSO, etc.). The hardware support (install, fix, E/C's, etc.) has mostly
been withdrawn from marketing.
That said, many hardware vendors (including IBM) will sell hardware support
contracts on older equipment,
Opps, this reply went to the wrong note. I noticed just after hitting send ...
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the
The following was sent in reply to the wrong note (my mistake).
IBM still supports the 3270 family of products in software (including OS's,
CICS, TSO, etc.). The hardware support (install, fix, E/C's, etc.) has mostly
been withdrawn from marketing.
That said, many hardware vendors (including
Have you tried the non-COBOL methods - put a hyphen (-) or backslash (\) on
the line to continue? (the manual says that the backslash is only for C/C++).
Or, maybe the COBOL method needs some sequence numbers in columns 1-6?
--
Unless you can really spread the workload across the 5 engines, I would go
with the 3 engine machine to be able to satisfy the largest single workload,
the production CICS LPAR.
On the other hand, you could build a compelling case for holding back
resources; put the production system on the 5
You forgot the 5840 - an even slower 580. The 580 series had three levels of
micro-code (I define micro-code in this context as software that runs on the
machine that the customer can not get to (display/alter/etc.) - that to the
customer, appears to be part of the hardware; in this broad
We've seen this before. It means that MQ thinks there is something it needs
to keep track of from that date. It could be a dead or orphaned message. Try
re-cycling (stop/start) the queue manager to free up the datasets, and then
manually delete the datasets (if MQ hasn't).
If the re-cycle
Try using:
http://www-03.ibm.com/systems/z/os/zos/bkserv/find_books.html
and enter your pub number, or other words in the title.
BTW, the keyword sg24-5444 pulled up the -03 rev of the document, which
includes the z/900.
--
To me, it sounds like this dataset is orphaned in the wrong usercat. You need
to temporary delete the alias to the correct usercat; delete the cluster with
the catalog parameter (or define the alias to the wrong usercat before the
delete); finally define the alias back to the correct usercat.
Hello Dennis,
I believe you are looking for an Escalation Procedure. The procedure can
take the form of a flow-chart, a table, or a written document.
The document (in whatever form) is best kept to a single page (it could be a
large page - like a folded 11x17). In the escalation document it
Do you have specific PTF that is causing this problem?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
The TLMS ALOG is the Alternate LOG, and used to do forward recovery on the
VMF (Volume Master File). Here are two snippets from the TLMS Systems
Programmers Guide:
TLMSUPDT—TLMSUPDT manages access to the Volume Master File at
the logical level. Records are retrieved from the VMF, updated with
I've set up a web page (really a html file on the Operator's PC, with a desktop
shortcut to the file) that has all of the information required (e.g. IP
name/address, IP port number (not 23), and LUNAME) for the TN3270 client
(ePassport from Zephyr Corp in our case). I wanted one desktop
We have the problem of keeping our z/OS 1.7 in sync with the rest of the
world here (lots of Windows and HP/UX). We looked at the sysplex timer, at
the time, the hardware was pricey, and the CPU (Amdahl Omniprise) could not
be order with the ETR feature (GOLC rules). Since then, we have moved
OK, that was my thread. After setting the SLIP trap, on the first go round I
didn't restrict GTF to only collecting SLIP entries (so I had lots of SVC's
etc.).
On the second go round, I had to clean up the directory in IPCS before I could
look at the trace (same dataset name, different
A new thread, called What subsystem ate my message? opened up and I
posted the following:
After setting the SLIP trap, on the first go round I
didn't restrict GTF to only collecting SLIP entries (so I had lots of SVC's
etc.).
On the second go round, I had to clean up the directory in IPCS
Hello everyone,
My operators are upset that the messages from doing a D R,R command are
being suppressed on the main console; they have to go to SDSF to see the
results. I can see in the SYSLOG that message IEE112I (the response from D
R,R) has a suppression flag of x'94' in the fourth byte
Offline, I was asked about the Automation package. We use CA-Opera, and
I've checked it out - it is not the culprit (I checked rules, and logs).
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Hello Patrick and Mark,
Thanks for the SLIP trap (and yes, THAT is what I was looking for). I'm
running z/OS 1.7, so with the same offsets for 1.6 1nd 1.8, I should be good. I
found a list of subsystems using SSI code 09 with MXI and TASID - I didn't
know about D SSI,FUNC=9 (it gave me a
39 matches
Mail list logo
