[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1143
  • Last Modified:

Refresh the mksysb resource on NIM

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
sminfo
Asked:
sminfo
1 Solution
 
woolmilkporcCommented:
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

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now