subrule parameter "filespace" does not work

daviddeleeuw1

ADSM.ORG Member
Joined
May 11, 2019
Messages
24
Reaction score
0
Points
0
PREDATAR Control23

I try to make a tape copy pool from our disk based container pool for selected filespaces.
I established a storage rule with action "nocopying".



Storage Rule Target Storage Target Server Action Active Source Storage
Name Pool Name Type Pools
--------------- --------------- --------------- -------- ------ ---------------
COPYPOOL TAPECOPY NoCopying No CPOOL


Now I wish to establish a subrule to choose the filesystems that should be copied.
I prefer working with FSID Nametypes, but this doesn't work. Typing a filespace name doesn't work as well.
Here are some examples of my attempts:

Protect: TSMMED>def subrule copypool medfs2copy medfs2 actiont=co filesp="31,55,56,57" namet=fsid
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - 31,55,56,57.
ANS8001I Return code 3.

def subrule copypool medfs2copy medfs2 actiont=co filesp=31,55,56,57 namet=fsid
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - 31,55,56,57.
ANS8001I Return code 3.

Protect: TSMMED>def subrule copypool medfs2copy medfs2 actiont=co filesp=31 namet=fsid
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - 31.
ANS8001I Return code 3.

Protect: TSMMED>def subrule copypool medfs2copy medfs2 actiont=co filesp="31" namet=fsid
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - 31.
ANS8001I Return code 3.

Protect: TSMMED>def subrule copypool medfs2copy medfs2 actiont=co filesp="\\medadmin\d$"
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - \\medadmin\d$.
ANS8001I Return code 3.


Ideas ?

Thanks

David
 
PREDATAR Control23

Protect: TSMMED>def subrule copypool medfs2copy medfs2 actiont=co filesp=31 namet=fsid
ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE parameter - 31.
ANS8001I Return code 3.


If your curious what Return Code 3 means -

RC_SYNTAX ERROR 3
The command is valid, but one or more parameters were not specified correctly.

Are we cut n' past the FSID number?
Or are we typing the FSID number?

Syntax looks correct.
What is the full version of the SP Server.
What os, and version, that is hosting the SP Server?

In the actlog what are the messages when we issue the "def subrule..."?
Can you post the messages in the actlog starting from when we issue the "def subrule" command?

Good Luck,
Sias
 
PREDATAR Control23

Dear Sias

Here are my answers on your questions:

Server on OS WINDOWS , Server 2019 Standard
Storage Protect Server Version 8, Release 1, Level 17.000


I typed all commands, no cut and paste.

Actlog:

17-01-2024 08:38:55 ANR2017I Administrator TSMUSER issued command: DEFINE
SUBRULE copypool medfs2copy medfs2 actiont=co filesp=31
namet=fsid (SESSION: 98637)
17-01-2024 08:38:55 ANR1998E DEFINE SUBRULE: Invalid value for FILESPACE
parameter - 31. (SESSION: 98637)
17-01-2024 08:38:55 ANR2017I Administrator TSMUSER issued command: ROLLBACK

(SESSION: 98637)

The node I am trying to backup is a client running a lot of shared filespaces. I only need a few of the filespaces in the pool.
So the filespace parameter is essential.


If you need more information, let me know.
Thanks

David
 
PREDATAR Control23

David,

... no cut and paste.

Okay. If we did cut and paste, more than likely there is a hidden character when we did the paste.

Storage Protect Server Version 8, Release 1, Level 17.000
At this time SP Sever 8.1.20.000 is the latest maintenance release.

The only APARs that I found:

IT41135: DEFINE SUBRULE FAILS WITH ANR1998E IF A WILDCARD (*) IS SPECIFIED FOR THE NODE NAMEAND IBM AUTO DEPLOY IS CONFIGURED.

IT40071: "INTERNAL ERROR" WITH HTTP 400 MESSAGE WHEN ADDING A NODE TO A SUBRULE IN IBM SPECTRUM PROTECT OPERATIONS CENTER 8.1.13

The above APARs does not apply with what we are encountering.

As for patch code, there is no patch code for 8.1.20.000.
I only found 8.1.16.100 , the fix is already included in 8.1.17.000

From the snippet of the actlog, there were no ANR9999D message or any odd message.
Just the same message when we issue the command that we got an invalid parameter.

Are we accessing the SP Server via remote desk top?
If we are using the remote desk top, it may be passing a hidden character.

The symptoms that we are encountering is like a typo or there is a hidden character.
If the issue was a bug, would expect to see an APAR.

If we are not accessing the SP Server via remote desk top.
May have to open a case with IBM and see if they have any idea.


Good Luck,
Sias
 
Top