406
MP Server / Re: Message 111 - OnDemand is unable to determine the link for the file
« on: January 10, 2019, 11:19:28 AM »
Does the arsmaint -v (validate) command show anything?
Ed
Ed
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
407
z/OS Server / Re: SQLR question
« on: January 04, 2019, 08:55:55 AM »
Had this come to me I would have started with an ODBC trace:
That should show the exact SQL statement causing the problem.
Ed
Quote
To take an ODBC trace:
Add the following entries [placed in the common section] to the
version of cli.ini pointed to by the DSNAOINI DD for ARSSOCKD:
APPLTRACEFILENAME=/tmp/arsodbctrace
APPLTRACE=1
An example cli.ini file:
[COMMON]
MVSDEFAULTSSID=DSNO
PLANNAME=DSNACLI
APPLTRACEFILENAME=/tmp/arsodbctrace
APPLTRACE=1
The output can be found in the HFS file pointed to by the
APPLTRACEFILENAME value.
That should show the exact SQL statement causing the problem.
Ed
408
z/OS Server / Re: SQLR question
« on: January 03, 2019, 11:14:43 AM »
Hi Steve - I didn't look up the messages or anything, but DECFLOAT rang a bell.
This is a little old, but make sure you aren't being bitten by this:
http://www.odusergroup.org/forums/index.php?topic=1525.msg5627#msg5627
Ed
This is a little old, but make sure you aren't being bitten by this:
http://www.odusergroup.org/forums/index.php?topic=1525.msg5627#msg5627
Ed
409
Windows Client / Re: Received error ARS0442E when upload document (file-add document)
« on: January 02, 2019, 01:32:52 PM »
Please do open a PMR.
In the meantime, try this:
You may need to add the following parameters to ars.cfg of the OnDemand server.
ARS_DOWNLOAD_DIR=
ARS_DOWNLOAD_TMP_DIR=
For example:
ARS_DOWNLOAD_DIR=/arstmp
ARS_DOWNLOAD_TMP_DIR=/arstmp
Then restart the OnDemand server and retest.
Here is a link to an FAQ on the subject.
http://www-01.ibm.com/support/docview.wss?uid=swg21686382
Ed
In the meantime, try this:
You may need to add the following parameters to ars.cfg of the OnDemand server.
ARS_DOWNLOAD_DIR=
ARS_DOWNLOAD_TMP_DIR=
For example:
ARS_DOWNLOAD_DIR=/arstmp
ARS_DOWNLOAD_TMP_DIR=/arstmp
Then restart the OnDemand server and retest.
Here is a link to an FAQ on the subject.
http://www-01.ibm.com/support/docview.wss?uid=swg21686382
Ed
410
MP Server / Re: Ondemand LibSrvr (ARCHIVE) service not starting at the first time.
« on: December 28, 2018, 08:35:14 AM »
Abhishek - this is not my area, but I do want to recommend upgrading to 10.1.0.4.
Running at the base level (10.1.0.0) and trying anything sophisticated...no sense trying to debug something that may already have been fixed.
Ed
Running at the base level (10.1.0.0) and trying anything sophisticated...no sense trying to debug something that may already have been fixed.
Ed
411
Windows Client / Re: Send (File Menu) OnDemand Client v9.5.0.3
« on: December 28, 2018, 08:32:41 AM »
The bitness of mail clients must match with the bitness of CMOD Windows client.
For example, if a 32-bit mail application is used, a 32-bit CMOD Windows client will work, but 64-bit Windows client will not.
If a 64-bit mail application is used, only a 64-bit Windows client will work.
Recommend you install the latest level of the 64 bit client and test.
Ed Arnold
For example, if a 32-bit mail application is used, a 32-bit CMOD Windows client will work, but 64-bit Windows client will not.
If a 64-bit mail application is used, only a 64-bit Windows client will work.
Recommend you install the latest level of the 64 bit client and test.
Ed Arnold
412
MP Server / Re: Version 9.5 with Spectrum Protect
« on: December 07, 2018, 06:05:27 PM »
And of course as soon as I made the previous append I found this:
http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI94940
That says that 9.5.0.11 fixed a problem with Spectrum 8.1.
So it looks like 9.5 is supported.
Ed
http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI94940
That says that 9.5.0.11 fixed a problem with Spectrum 8.1.
So it looks like 9.5 is supported.
Ed
413
MP Server / Re: Version 9.5 with Spectrum Protect
« on: December 07, 2018, 05:52:12 PM »
I think you need to get on 10.1.
Reason:
V10.1
If you go here:
https://www-01.ibm.com/support/docview.wss?uid=swg27049167
Then click on the link to render the chart and select the Prerequisites tab and then go down to the bottom you'll see Spectrum Connect 8.1 listed.
V9.5
If you go here:
https://www-01.ibm.com/support/docview.wss?uid=swg27043162
Then click on the link to render the chart, select the 9.5.0.12 pulldown, then select the Prerequisites tab and then go down to the bottom you see
IBM Tivoli Storage Manager Client 6.4 and future fix packs.
Future fix packs, not future releases.
Ed
Reason:
V10.1
If you go here:
https://www-01.ibm.com/support/docview.wss?uid=swg27049167
Then click on the link to render the chart and select the Prerequisites tab and then go down to the bottom you'll see Spectrum Connect 8.1 listed.
V9.5
If you go here:
https://www-01.ibm.com/support/docview.wss?uid=swg27043162
Then click on the link to render the chart, select the 9.5.0.12 pulldown, then select the Prerequisites tab and then go down to the bottom you see
IBM Tivoli Storage Manager Client 6.4 and future fix packs.
Future fix packs, not future releases.
Ed
414
z/OS Server / Re: 10.1 Release Notes
« on: December 07, 2018, 12:06:36 PM »
If you're using the old style parms on ARSSOCKD - or no parms at all - it's time to use the new parms when you roll out V10.1.
For example:
If you start ARSSOCKD with no parms at all that's fine, it means you're taking all of the defaults:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT
Recommend you change that when you initially bring up V10 to the following:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM='/-S -I ARCHIVE -v'
Why? Two reasons.
1. The -v means verbose. All it does is echo the parms in effect to SYSOUT. It costs nothing in performance, no traces, nothing like that. It makes seeing what parms you have in effect (and communicating to that support) far easier than copying the ars.cfg and ars.ini files.
2. If requested to add a trace, it now becomes simple:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
//* PARM='/-S -I ARCHIVE -v'
// PARM='/-S -I ARCHIVE -v -1 /tmp/ed.trc -2 ALL=15'
The -1 parm gives the path and file name for where to put the trace and the ALL=15 tells it trace everything.
In the preceding example to start a trace all you have to do is comment out the first parm line and uncomment the second and recycle ARSSOCKD. Easy!
________________________________________________
If you start ARSSOCKD with parms that look something this
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/NEWARCH ARSSOCKD')
then change that to
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I NEWARCH -v')
Some shops already have VERBOSE on the old style parm line:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/INSTANCE ARSSOCKD VERBOSE')
then change that to effectively the same thing, but still, the way to pre-position tracing parameters:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I INSTANCE -v')
//*PARM=('/-S -I INSTANCE -v -1 /tmp/ed.trc -2 ALL=15')
Ed
For example:
If you start ARSSOCKD with no parms at all that's fine, it means you're taking all of the defaults:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT
Recommend you change that when you initially bring up V10 to the following:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM='/-S -I ARCHIVE -v'
Why? Two reasons.
1. The -v means verbose. All it does is echo the parms in effect to SYSOUT. It costs nothing in performance, no traces, nothing like that. It makes seeing what parms you have in effect (and communicating to that support) far easier than copying the ars.cfg and ars.ini files.
2. If requested to add a trace, it now becomes simple:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
//* PARM='/-S -I ARCHIVE -v'
// PARM='/-S -I ARCHIVE -v -1 /tmp/ed.trc -2 ALL=15'
The -1 parm gives the path and file name for where to put the trace and the ALL=15 tells it trace everything.
In the preceding example to start a trace all you have to do is comment out the first parm line and uncomment the second and recycle ARSSOCKD. Easy!
________________________________________________
If you start ARSSOCKD with parms that look something this
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/NEWARCH ARSSOCKD')
then change that to
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I NEWARCH -v')
Some shops already have VERBOSE on the old style parm line:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/INSTANCE ARSSOCKD VERBOSE')
then change that to effectively the same thing, but still, the way to pre-position tracing parameters:
//ONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,
// PARM=('/-S -I INSTANCE -v')
//*PARM=('/-S -I INSTANCE -v -1 /tmp/ed.trc -2 ALL=15')
Ed
415
Tips and Tricks / Re: Adding Page Counts, Document Size (in bytes), Doc Type and Load Time/Date to App
« on: November 27, 2018, 09:25:46 AM »
Here's a copy.
Ed
Ed
416
z/OS Server / Re: ARS0430E
« on: November 12, 2018, 07:25:20 AM »
Håkan - you got me on that one.
Still -
Because processes with process limits contribute to the total amount of allocated mmap pages, processes limited by the MAXMMAPAREA value might fail an mmap request before a BPXI039I message is issued.
I recommend a MMAPAREAMAX= NONE for that parm. I have yet to hear anything good of setting any limits on that parm, either at the TSO level or at the OMVS level.
And my display from D OMVS,O says my setting is MAXMMAPAREA = 120000
Ed
Still -
Because processes with process limits contribute to the total amount of allocated mmap pages, processes limited by the MAXMMAPAREA value might fail an mmap request before a BPXI039I message is issued.
I recommend a MMAPAREAMAX= NONE for that parm. I have yet to hear anything good of setting any limits on that parm, either at the TSO level or at the OMVS level.
And my display from D OMVS,O says my setting is MAXMMAPAREA = 120000
Ed
417
z/OS Server / Re: ARS0430E
« on: November 08, 2018, 08:54:32 AM »
16777216 or 16,777,216? Doesn't sound like much.
If I do a TSO LU userid NORACF OMVS on the userid for ARSSOCKD on V10 I get:
UID= 0000000569
HOME= /u/arssv100
PROGRAM= /bin/sh
CPUTIMEMAX= NONE
ASSIZEMAX= NONE
FILEPROCMAX= NONE
PROCUSERMAX= NONE
THREADSMAX= NONE
MMAPAREAMAX= NONE
For the console command D OMVS,O I get:
MAXMMAPAREA = 120000
Ed
If I do a TSO LU userid NORACF OMVS on the userid for ARSSOCKD on V10 I get:
UID= 0000000569
HOME= /u/arssv100
PROGRAM= /bin/sh
CPUTIMEMAX= NONE
ASSIZEMAX= NONE
FILEPROCMAX= NONE
PROCUSERMAX= NONE
THREADSMAX= NONE
MMAPAREAMAX= NONE
For the console command D OMVS,O I get:
MAXMMAPAREA = 120000
Ed
418
z/OS Server / Direct Load Info
« on: November 06, 2018, 01:01:40 PM »
To do a Direct Load one of the conditions is the userid must match between the load job and arssockd.
What exactly is getting used?
If you look at a trace for arsload, for example:
83888142:4197548366755790848 06/25/2014 16:57:33:946476 INFO
SYS13344.T124629.RA000.ARNLOAD.SRCCMS.H01(ARNLOAD)(2203)
ArcLOADP_startup _390:Running TCPIP Instance
HOST=ARSAA00A rsn_text_u=Ident failed for
ARSAA00A.3009.ARSSERVR.OD390SA
Then:
ARSAA00A - instance
3009 - port
ARSSERVR - RACF user
OD390SA - RACF group
for the arsload.
That RACF user has to match the what is used by the server.
________________________
If you want to find out what the server is using all you have to do is issue the GRS command:
D GRS,RES=(SYSZARSI,*)
This is the result from my system:
RESPONSE=MVS222
ISG343I 14.35.44 GRS STATUS 765
S=SYSTEM SYSZARSI ARCH950.11449.ARSSV950.ODCMARS
SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS
MVS222 ARSSOC95 003E 008F8588 SHARE OWN
Note the ARCH950.11449.ARSSV950.ODCMARS.
Ed
What exactly is getting used?
If you look at a trace for arsload, for example:
83888142:4197548366755790848 06/25/2014 16:57:33:946476 INFO
SYS13344.T124629.RA000.ARNLOAD.SRCCMS.H01(ARNLOAD)(2203)
ArcLOADP_startup _390:Running TCPIP Instance
HOST=ARSAA00A rsn_text_u=Ident failed for
ARSAA00A.3009.ARSSERVR.OD390SA
Then:
ARSAA00A - instance
3009 - port
ARSSERVR - RACF user
OD390SA - RACF group
for the arsload.
That RACF user has to match the what is used by the server.
________________________
If you want to find out what the server is using all you have to do is issue the GRS command:
D GRS,RES=(SYSZARSI,*)
This is the result from my system:
RESPONSE=MVS222
ISG343I 14.35.44 GRS STATUS 765
S=SYSTEM SYSZARSI ARCH950.11449.ARSSV950.ODCMARS
SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS
MVS222 ARSSOC95 003E 008F8588 SHARE OWN
Note the ARCH950.11449.ARSSV950.ODCMARS.
Ed
419
MP Server / Re: TSM Question - Upgrades?
« on: November 06, 2018, 08:49:39 AM »
-> I do not know the answer to this latest issue but I can make an educated guess. <-
Command Line Administrative Interface - Version 6, Release 2, Level 0.0
That looks like a subcomponent of TSM that has its own version/release/modification tracking.
Ed
Command Line Administrative Interface - Version 6, Release 2, Level 0.0
That looks like a subcomponent of TSM that has its own version/release/modification tracking.
Ed
420
z/OS Server / Re: ARS0430E
« on: November 06, 2018, 07:17:49 AM »
That's a message that we see on rare occasion.
-> If you're lucky, <- check your MAXMMAPAREA setting in OMVS, recommended is at least 120000, recycle the ARSSOCKD started task and see if the problem recurs.
If you still have the problem either open a PMR -or- if you're not on a supported level of CMOD let me know here and I'll see what I can do.
Ed
-> If you're lucky, <- check your MAXMMAPAREA setting in OMVS, recommended is at least 120000, recycle the ARSSOCKD started task and see if the problem recurs.
If you still have the problem either open a PMR -or- if you're not on a supported level of CMOD let me know here and I'll see what I can do.
Ed