Sponsored Content
Top Forums UNIX for Dummies Questions & Answers nim mksysb - 0042-124 c_ch_nfsexp error Post 302223669 by astjen on Monday 11th of August 2008 04:39:46 AM
Old 08-11-2008
nim mksysb - 0042-124 c_ch_nfsexp error

Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 979345 (957 MB) Available = 10474116 (10229 MB)
Creating information file (/image.data) for rootvg.
/usr/bin/savevg[33]: 1016,07: syntax error
0042-001 nim : pocessing error detected "master" :
0042-124 c_ch_nfsexp : option NFS sec=sys isn't supported

rc=1
0042-001 m_mkbosi : processing error detected on "client_1" :
 

10 More Discussions You Might Find Interesting

1. AIX

NIM mksysb recovery

I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level My understanding is creating mksysb nim on NIM server is for new installation of LPARS Then; How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies

2. UNIX for Advanced & Expert Users

NIM - mksysb of remote server

Hi, I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network. I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows Resource Name : gmt_fail_mksysb Server of... (1 Reply)
Discussion started by: KeesH
1 Replies

3. Shell Programming and Scripting

script to automate mksysb via nim in AIX 5.3

#!/bin/ksh # # nim_mksysb # get mksysb from each client machine specified with -m. If no # machines specified, get mksysb from ALL machines. -r flag says # remove oldest existing mksysb for the machines being backed up. # use -n no_make flag with -r to remove a generation of mksysb, #... (0 Replies)
Discussion started by: barkath
0 Replies

4. AIX

NIM client mksysb restore

Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies

5. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

6. AIX

nim mksysb buffer overflow error

Hi, I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master") The backup starts, but doesn't success. Thanks if you can help me to resolve this problem : Creating information file (/image.data) for rootvg... Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies

7. AIX

how to create a package from mksysb via nim ?

Hello, I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5). How to install it from a nim mksysb of an another partition ? Thank you (3 Replies)
Discussion started by: astjen
3 Replies

8. AIX

AIX 5L nim mksysb command

Hi All, Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like? Does it even remotely resemble something like nim -o... (1 Reply)
Discussion started by: combustables
1 Replies

9. AIX

mksysb restoration using NIM

Hi, I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies

10. AIX

mksysb using NIM

I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root. Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies
FMTMSG(3)						   BSD Library Functions Manual 						 FMTMSG(3)

NAME
fmtmsg -- display a detailed diagnostic message LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <fmtmsg.h> int fmtmsg(long classification, const char *label, int severity, const char *text, const char *action, const char *tag); DESCRIPTION
The fmtmsg() function displays a detailed diagnostic message, based on the supplied arguments, to stderr and/or the system console. The classification argument is the bitwise inclusive OR of zero or one of the manifest constants from each of the classification groups below. The Output classification group is an exception since both MM_PRINT and MM_CONSOLE may be specified. Output MM_PRINT Output should take place on stderr. MM_CONSOLE Output should take place on the system console. Source of Condition (Major) MM_HARD The source of the condition is hardware related. MM_SOFT The source of the condition is software related. MM_FIRM The source of the condition is firmware related. Source of Condition (Minor) MM_APPL The condition was detected at the application level. MM_UTIL The condition was detected at the utility level. MM_OPSYS The condition was detected at the operating system level. Status MM_RECOVER The application can recover from the condition. MM_NRECOV The application is unable to recover from the condition. Alternatively, the MM_NULLMC manifest constant may be used to specify no classification. The label argument indicates the source of the message. It is made up of two fields separated by a colon (':'). The first field can be up to 10 bytes, and the second field can be up to 14 bytes. The MM_NULLLBL manifest constant may be used to specify no label. The severity argument identifies the importance of the condition. One of the following manifest constants should be used for this argument. MM_HALT The application has confronted a serious fault and is halting. MM_ERROR The application has detected a fault. MM_WARNING The application has detected an unusual condition, that could be indicative of a problem. MM_INFO The application is providing information about a non-error condition. MM_NOSEV No severity level supplied. The text argument details the error condition that caused the message. There is no limit on the size of this character string. The MM_NULLTXT manifest constant may be used to specify no text. The action argument details how the error-recovery process should begin. Upon output, fmtmsg() will prefix "TO FIX:" to the beginning of the action argument. The MM_NULLACT manifest constant may be used to specify no action. The tag argument should reference online documentation for the message. This usually includes the label and a unique identifying number. An example tag is "BSD:ls:168". The MM_NULLTAG manifest constant may be used to specify no tag. RETURN VALUES
The fmtmsg() function returns MM_OK upon success, MM_NOMSG to indicate output to stderr failed, MM_NOCON to indicate output to the system console failed, or MM_NOTOK to indicate output to stderr and the system console failed. ENVIRONMENT
The MSGVERB (message verbosity) environment variable specifies which arguments to fmtmsg() will be output to stderr, and in which order. MSGVERB should be a colon (':') separated list of identifiers. Valid identifiers include: label, severity, text, action, and tag. If invalid identifiers are specified or incorrectly separated, the default message verbosity and ordering will be used. The default ordering is equivalent to a MSGVERB with a value of "label:severity:text:action:tag". EXAMPLES
The code: fmtmsg(MM_UTIL | MM_PRINT, "BSD:ls", MM_ERROR, "illegal option -- z", "refer to manual", "BSD:ls:001"); will output: BSD:ls: ERROR: illegal option -- z TO FIX: refer to manual BSD:ls:001 to stderr. The same code, with MSGVERB set to "text:severity:action:tag", produces: illegal option -- z: ERROR TO FIX: refer to manual BSD:ls:001 SEE ALSO
err(3), exit(3), strerror(3) STANDARDS
The fmtmsg() function conforms to IEEE Std 1003.1-2001 (``POSIX.1''). HISTORY
The fmtmsg() function first appeared in FreeBSD 5.0. BUGS
Specifying MM_NULLMC for the classification argument makes little sense, since without an output specified, fmtmsg() is unable to do anything useful. In order for fmtmsg() to output to the system console, the effective user must have appropriate permission to write to /dev/console. This means that on most systems fmtmsg() will return MM_NOCON unless the effective user is root. BSD
August 5, 2002 BSD
All times are GMT -4. The time now is 03:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy