Browse Community
Help
Log In
Responses(6)
Solutions(1)
bingo.1
2.4K Posts
0
April 11th, 2018 11:00
Sorry - I did not look at the pathnames. You need to a line that applies to this specific directory (tree).
The standard directive does not apply to "/opt...."
The line should read like
<< /opt >> or whatever directory you want to start with
+logasm: .
MickC1975
23 Posts
April 5th, 2018 05:00
Thanks Bingo, I can have a look at this.
So you don't think the authentication error on the line above is relevant?
Regards
Michael
1
Such indicates that the file changed from creating the worklist until it will be backed up. Obvious for log files.
NW should notice the changes but this should not result in an error.
To overcome the issue you should apply the UNIX standard directive which used 'logasm' to suppress these messages.
To learn more about directives, please see the Command Line Reference manual (uasm).
April 5th, 2018 07:00
I think it is irrelevant. But let's see what you will get after you applied the directive.
April 11th, 2018 03:00
Hi Bingo
We applied the UNIX directive but are still getting the same error. Any further ideas?
April 16th, 2018 23:00
Cheers Bingo, that seems to have worked.
Thanks for your help
Dell Support Resources
View All
Top
bingo.1
2.4K Posts
0
April 11th, 2018 11:00
Sorry - I did not look at the pathnames. You need to a line that applies to this specific directory (tree).
The standard directive does not apply to "/opt...."
The line should read like
<< /opt >> or whatever directory you want to start with
+logasm: .
MickC1975
23 Posts
0
April 5th, 2018 05:00
Thanks Bingo, I can have a look at this.
So you don't think the authentication error on the line above is relevant?
Regards
Michael
bingo.1
2.4K Posts
1
April 5th, 2018 05:00
Such indicates that the file changed from creating the worklist until it will be backed up. Obvious for log files.
NW should notice the changes but this should not result in an error.
To overcome the issue you should apply the UNIX standard directive which used 'logasm' to suppress these messages.
To learn more about directives, please see the Command Line Reference manual (uasm).
bingo.1
2.4K Posts
0
April 5th, 2018 07:00
I think it is irrelevant. But let's see what you will get after you applied the directive.
MickC1975
23 Posts
0
April 11th, 2018 03:00
Hi Bingo
We applied the UNIX directive but are still getting the same error. Any further ideas?
Regards
Michael
MickC1975
23 Posts
0
April 16th, 2018 23:00
Cheers Bingo, that seems to have worked.
Thanks for your help
Michael