When a z/OS UNIX C/C++ application program is running in an address space created as a result of a call to spawnp(), vfork(), or one of the exec family of functions, the SYSMDUMP DD allocation information is not inherited. Even though the SYSMDUMP allocation is not inherited, a SYSMDUMP allocation must exist in the parent in order to obtain a HFS storage dump.
Alternatively, you can specify the DYNDUMP runtime option to generate a system dump. For more information, see z/OS Language Environment Programming Reference.
/directory/coredump.pid
-------------------------- DATA SET INFORMATION ----------------------
Command ===>
Data Set Name . . . : URCOMP.JRUSL.COREDUMP
General Data Current Allocation
Management class . . : STANDARD Allocated cylinders : 30
Storage class . . . : OS390 Allocated extents . : 1
Volume serial . . . : DPXDU1
Device type . . . . : 3380
Data class . . . . . :
Organization . . . : PS Current Utilization
Record format . . . : FB Used cylinders. . . : 0
Record length . . . : 4160 Used extents . . . : 0
Block size . . . . : 4160
1st extent cylinders: 30
Secondary cylinders : 10
Data set name type :
Creation date . . . : 2001/08/30
Expiration date . . : ***None***
F1=Help F2=Split F3=End F4=Return F5=Rfind F6=Rchange
F7=Up F8=Down F9=Swap F10=Left F11=Right F12=Cancel
Fill in the information for your data set as shown, and estimate the number of cylinders required for the dump file you are going to copy.
OGET '/u/urcomp/coredump.00060007' 'urcomp.jrusl.coredump' BINARY
For more information on using the copy commands, see z/OS UNIX System Services User's Guide .
After you have copied the storage dump file to the data set, you can use IPCS to analyze the dump. See Formatting and analyzing system dumps for information about formatting Language Environment control blocks.