- Welcome, Guest. Please Login or Register
Telcom Pro's - Switch Technicians unite!  
   
  HomeHelpSearchLoginRegister   
     
     
   
 
Page Index Toggle Pages: 1 Send Topic Print  
scanf error
Read 192 times

milton   Offline
Full Member
NOC Technician

****
Posts: 101


   
     
 
scanf error
Sep 24th, 2020 at 11:53pm
 
I am trying to copy a file from one slm disk vol to another slm disk vol;

scanf s01dpmld copy s00dpmld name abc14yz

and I get...
Scanf copy result: Device error (4)
ABC14YZ: create destination file failed.
Scanf: Copied 0 of the 405 files encountered

The file exists on s01dpmld and does not on s00dpmld

Do I have a syntax problem? permission problem?

Thanks for your help
 
 
 
IP Logged    
 
     

1palm   Offline
Senior Member
Switch Technician

*****
Posts: 498


   
     
 
Re: scanf error
Reply #1 - Sep 25th, 2020 at 3:21pm
 
Syntax looks correct. Can you scanf to the sfdev or another device (as if the destination device might be full or faulty)? Can you scanf the opposite direction? Also is that the full file name, any reason to think there could be any hidden characters? When you list the donor volume is the file name in upper or lower case, etc?

Working syntax examples, both SLM and DDU:

>scanf s00dpatch copy s01dpatch name XLO21X14$PATCH
Copy file: XLO21X14$PATCH
    10% - 6 recs
    20% - 12 recs
    30% - 18 recs
    40% - 24 recs
    50% - 30 recs
    60% - 36 recs
    70% - 42 recs
    80% - 48 recs
    90% - 54 recs
    100% - 60 recs
XLO21X14$PATCH: 66 records copied with success.
Scanf: Copied 1 of the 422 files encountered.

>scanf d030sb3 copy d020sb2 name LMC_ABORT_CS
Copy file: LMC_ABORT_CS
    10% - 20 recs
    20% - 40 recs
    30% - 60 recs
    40% - 80 recs
    50% - 100 recs
    60% - 120 recs
    70% - 140 recs
    80% - 160 recs
    90% - 180 recs
    100% - 200 recs
LMC_ABORT_CS: 202 records copied with success.
Scanf: Copied 1 of the 277 files encountered.
 
 
 
IP Logged    
 
     

milton   Offline
Full Member
NOC Technician

****
Posts: 101


   
     
 
Re: scanf error
Reply #2 - Sep 25th, 2020 at 8:48pm
 
thanks 1palm,
below is the volume info for both SLM disks
I can copy from s01dpmld to sfdev.
I can not copy to s00dpmld from either s01dpmld or sfdev
I can copy from s00dpmld to s01dpmld (but I don't need to do this)
Also below is the scanf full output of the actual file I'm trying to copy, it's missing from s00dpmld and causing a PMLOAD alarm

>volinfo s00dpmld
Information for disk volume S00DPMLD on node CM   :
{Note: 1 BLOCK = 512 BYTES.}
----------------------------------------------

Name                          : PMLD   
Type                          : STD
Status                        : OPENED
When last modified            : 2002/12/09 13:10:54.984 MON.
# files on volume             : 409
# open files                  : 0
# writers                     : 0
# files registered in ITOCs   : 0
# blocks                      : 409473
# blocks in use               : 181858
# free blocks                 : 227615
Size of largest free segment  : 173224
# free segments               : 10

>volinfo s01dpmld
Information for disk volume S01DPMLD on node CM   :
{Note: 1 BLOCK = 512 BYTES.}
----------------------------------------------

Name                          : PMLD   
Type                          : STD
Status                        : OPENED
When last modified            : 2002/12/09 15:04:29.101 MON.
# files on volume             : 405
# open files                  : 0
# writers                     : 0
# files registered in ITOCs   : 0
# blocks                      : 409473
# blocks in use               : 172019
# free blocks                 : 237454
Size of largest free segment  : 190734
# free segments               : 14

>scanf s01dpmld full name ecl14bc

File Name        : ECL14BC (7 chars)
Owner            : * no owner * (0 chars)
Record Length    : 1024b
Number of Records: 2931 (2931)
Open Status      : OPEN FOR WRITE
Attributes       : -f-----
Number of Blocks : 5887
Created On       : 2002/12/09 15:14:24.520 MON.
File Code        : 0
Modified On      : 2002/12/09 15:14:24.520 MON.
Number of Extents: 1
Additional file information:
Scanf: Listed 1 of the 405 files encountered.
 
 
 
IP Logged    
 
     

1palm   Offline
Senior Member
Switch Technician

*****
Posts: 498


   
     
 
Re: scanf error
Reply #3 - Sep 28th, 2020 at 3:17pm
 
HI Milton,

Can you copy to any other volume on SLM-0 or is it just the pmld volume giving trbls?
 
 
 
IP Logged    
 
     

milton   Offline
Full Member
NOC Technician

****
Posts: 101


   
     
 
Re: scanf error
Reply #4 - Sep 29th, 2020 at 11:20am
 
strange...
I just tried your suggestion and I was able to successfully copy from S01DPMLD to 2 other volumes on SLM-0
Next I tried to copy from S00DSCRATCH to S00DPMLD and got the error;

Scanf copy result: Device error (4)

So, something seems to be wrong with SOODPMLD and with 227615 free blocks I don't think it's a space issue

Thanks again for your input
 
 
 
IP Logged    
 
     

1palm   Offline
Senior Member
Switch Technician

*****
Posts: 498


   
     
 
Re: scanf error
Reply #5 - Sep 29th, 2020 at 3:18pm
 
You may have to check into the health of pmld volume itself, perhaps reallocate it, etc. If there's a lot of DIRP related subsystems (esp AMA) on that SLM the prep work might be important (eg dirpcopy of files and the like). The solution seems to be trending that direction....
 
 
 
IP Logged    
 
     

1palm   Offline
Senior Member
Switch Technician

*****
Posts: 498


   
     
 
Re: scanf error
Reply #6 - Sep 29th, 2020 at 3:41pm
 
One other thought: Did you try a regular old "copy" command to the SLM vol? That might help rule in/out your options......
 
 
 
IP Logged    
 
     

milton   Offline
Full Member
NOC Technician

****
Posts: 101


   
     
 
Re: scanf error
Reply #7 - Sep 30th, 2020 at 1:51pm
 
Thank you 1palm,
Per your advise, I tried to just plain old copy to s00dpmld buy the operation failed with a device error, so it does appear something is wrong with the volume.

Fortunately all dirp files are written to ddu so it's just the pmload files.

Temporarily, I copied missing pmload files to s00dpatch and modified table pmloads to reflect the new location so the pmload alarm has cleared.

I'll leave the decision making to the higher ups regarding the reallocation of the problem disk volume.

Cheers for the helpful advise
 
 
 
IP Logged    
 
     
Page Index Toggle Pages: 1 Send Topic Print  
Bookmarks
Google Digg del.icio.us Facebook reddit Twitter Linked in MySpace StumbleUpon Yahoo