Solved

Refresh the mksysb resource on NIM

Posted on 2011-03-17
1
1,118 Views
Last Modified: 2013-11-17
ok,

I have created multiples mksysb that are located on:
MKSYSB_MIDDLEPRE:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = ready for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/middlepre/middlepre.img
   version       = 6
   release       = 1
   mod           = 6
   oslevel_r     = 6100-06
   alloc_count   = 0
   server        = master
   creation_date = Thu Mar 17 14:59:30 2011

MKSYSB_BIBMDES_CONT:
   class         = resources
   type          = mksysb
   Rstate        = ready for use
   prev_state    = ready for use
   nfs_vers      = 3
   nfs_sec       = sys
   location      = /LPAR_MKSYSB/bibmdes_cont/contingencia.img
   version       = 5
   release       = 3
   mod           = 12
   oslevel_r     = 5300-12
   alloc_count   = 0
   server        = master
   creation_date = Wed Mar 16 18:09:52 2011


MKSYSB_MIDDLEDES:
   class          = resources
   type           = mksysb
   Rstate         = ready for use
   prev_state     = ready for use
   nfs_vers       = 3
   nfs_sec        = sys
   location       = /LPAR_MKSYSB/middledes/middledes.img
   version        = 6
   release        = 1
   mod            = 6
   oslevel_r      = 6100-06
   alloc_count    = 0
   server         = master
   extracted_spot = spotbibm
   creation_date  = Thu Mar 17 12:23:57 2011

Every week these mksysb files are updated (note: all mksysb will have the same TL), so the question is:

Do I have to refresh or to do something on the NIM server if the content of the mksysb file  change?

I assume that if I change the TL on the mksysb file I have to recreate the resource, no?

This NIM is driving me crazyyyyyyy
:-)
0
Comment
Question by:sminfo
1 Comment
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 35158379
I always use "nim -o define -t mksysb -a source=nim_client ..." to have NIM pull an mksysb from the node,
instead of running mksysb there to write it to an NFS mount served by NIM.

This way NIM has always full control of the process and can refresh its database if needed.

Of course you must remove the old mksysb first, use "nim -o remove mksysb_resource" for this.

If you use to create the mksysb outside of NIM maybe this is the reason for all your trouble.

If you don't want NIM to create the image itself at least delete and redefine the NIM mksysb resource (not the underlying image) each time you create a new image.
Delete first, then take image, then define NIM resource to avoid deletion of your new image by NIM.

wmp
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

This tech tip describes how to install the Solaris Operating System from a tape backup that was created using the Solaris flash archive utility. I have used this procedure on the Solaris 8 and 9 OS, and it shoudl also work well on the Solaris 10 rel…
Java performance on Solaris - Managing CPUs There are various resource controls in operating system which directly/indirectly influence the performance of application. one of the most important resource controls is "CPU".   In a multithreaded…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now