We just installed a z10 processor this morning, and the Dirmaint satellite
on it won¹t install a directory. The message I get says that there is no
DIRECTORY statement which matches the serial and model number, and then has
the serial and model in parens. OK, so I cut and paste the serial and
... and good stuff too from Melinda Varian and others on the Distribution
Page ...
http://vm.marist.edu/~pipeline/
http://vm.marist.edu/~pipeline/#MWV
You've got the model from Q CPUID? (a z10 BC is a 2098, an EC is a 2097)
No hex 41 somewhere? SET OUTPUT 41 _ can make those visible.
The DIRMSAT has no CPUID statement in its directory entry? So CP FOR
DIRMSAT CMD Q CPUID can help.
2011/3/20 RPN01 nix.rob...@mayo.edu
We just installed a
I recall using SET CPUID (command or directory) to make yourself immune to
the system CPUID changing..
- Set the DIRMAINT guests (DIRMAINT/DIRMSAT/DATAMOVE) to a simple CPUID
number (e.g. 1)
- Use the CPUID in the directory (1)
- Use different numbers if you need to distinguish between
On Sunday, 03/20/2011 at 05:53 EDT, RPN01 nix.rob...@mayo.edu wrote:
We just installed a z10 processor this morning, and the Dirmaint
satellite on
it won?t install a directory. The message I get says that there is no
DIRECTORY
statement which matches the serial and model number, and then
The work space is not allocated the same way if control and logs have many
blocks defined or not. I did several tests to suit my needs and i remarked that
dasd pages could be used or (vs. Memory) not depending of what coded in the
pooldef file. That seems normal anyway to me and glad to see
