Skip to main content

alphaWorks  >  Forums  >  Scripting Tools for SAN Volume Controller  >  developerWorks

commands with no arguments    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Permlink Replies: 1 - Pages: 1 - Last Post: Apr 13, 2009 4:44 AM Last Post By: assaf Threads: [ Previous | Next ]
assaf

Posts: 2
Registered: Apr 13, 2009 03:37:01 AM
commands with no arguments
Posted: Apr 13, 2009 03:45:33 AM
 
Click to report abuse...   Click to reply to this thread Reply
Hey guys,

I've just downloaded and started to use this great package.
I quickly ran into a small problem I'm which I'm having problems working
around.
The thing is, whenever I try issuing an svcinfo/svctask command with no arguments,
I get several error massages saying that a few lines in the SVC.pm file use
uninitialized values.

I'm quite new to perl, so maybe it's just an error of use on my part.
has anyone else ran into that problem?

Many thanks,

Assaf

P.S - for example:
while issuing any of the following code lines, I get the same error message:
my ($rc, $info_ref) = $svc->svcinfo("lsrcrelationship");
my ($rc, $info_ref) = $svc->svcinfo("lsrcrelationship", {});
my ($rc, $info_ref) = $svc->svcinfo("lsrcrelationship", {}, "");

error msg:
Use of uninitialized value $object in length at C:/Perl/lib/IBM/SVC.pm line 199.
Use of uninitialized value $object in length at C:/Perl/lib/IBM/SVC.pm line 199.
Use of uninitialized value $header_row in pattern match (m//) at C:/Perl/lib/IBM/SVC.pm line 362.
Use of uninitialized value $header_row in scalar chomp at C:/Perl/lib/IBM/SVC.pm line 367.
Use of uninitialized value $header_row in split at C:/Perl/lib/IBM/SVC.pm line 368.
assaf

Posts: 2
Registered: Apr 13, 2009 03:37:01 AM
a partial workaround
Posted: Apr 13, 2009 04:44:12 AM   in response to: assaf in response to: assaf's post
 
Click to report abuse...   Click to reply to this thread Reply
I found out that this warnings occur only when with the -w flag.
however, without that flag, I'm missing a lot of warnings in my own
code.

Point your RSS reader here for a feed of the latest messages in all forums