A fix is available
APAR status
Closed as new function.
Error description
The data rate to DASD may not be optimal in some conditions, when writing a stand alone dump (SADMP).
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Stand-alone dump (SADMP) users * * at HBB7790 and above * **************************************************************** * PROBLEM DESCRIPTION: New function to improve Stand-alone * * dump (SADMP) capture times. * **************************************************************** * RECOMMENDATION: * **************************************************************** Note that these functions are already available in HBB77A0, however, minor fixes are provided with this APAR. This is a new function APAR which improves the Stand-alone dump (SADMP) capture time by providing the following: - More efficient method for output I/O operations. - Support a new parameter REAL=ALL|USED for AMDSADMP macro. - Support new SADMPNO option on the SADMP generation program. SADMP=YES|NO support for 64-bit virtual storage is provided by Storage service's OA47439.
Problem conclusion
Temporary fix
Comments
Stand-alone dump was updated to provide needed support to improve capture times. The following documentation updates will be made. z/OS MVS Diagnosis: Tools and Service Aids, GA32-0905 Chapter: Stand-alone dump Topic: Stand-alone dump The stand-alone dump program (SADMP) produces a stand-alone dump of storage that is occupied by one of the following: - A system that failed. - A stand-alone dump program that failed. Either the stand-alone dump program dumped itself - a self-dump -, or the operator loaded another stand-alone dump program to dump the failed stand-alone dump program. The stand-alone dump program and the stand-alone dump together form what is known as the stand-alone dump service aid. The term stand-alone means that the dump is performed separately from normal system operations and does not require the system to be in a condition for normal operation. The stand-alone dump program produces a high-speed, | unformatted dump of all of central storage, plus it can | include user tailorable parts of paged-out virtual storage. | The user generated stand-alone dump program must reside on | a storage device that can be used to IPL from. Topic: If I do dump to DASD, how much space do I need? The maximum size of a single-volume DASD dump data set depends on the type of data set. | . Conventional sequential (DSNTYPE=BASIC) data sets can | span 65,535 tracks per volume, and can hold approximately | 3 GB per volume. | . Extended format (DSNTYPE=EXTREQ) data sets are supported | by z/OS V1R6 and later releases. Extended format | sequential data sets can hold 4,294,967,295 blocks per | volume. The maximum size for extended format sequential | is approximately 98,304 GB per volume. You cannot use | striping or compression options for extended format | sequential data sets. You must use the guaranteed free | space option to require DFSMS to reserve space at the | time that the data set is created. | . Large format data sets are supported by z/OS V1R7 and | later releases. Large format (DSNTYPE=LARGE) data sets | can span 16,777,215 tracks per volume. The maximum size | for large format data sets is approximately 768 GB per | volume. If you require more space than you want to allocate on a single volume, you can define a multi-volume DASD data set that can span up to 32 volumes of the same device type. | Note: Beginning in z/OS V1R12, SADMP supports placement of | dump data sets in cylinder-managed space. In releases | prior to z/OS V1R12, stand-alone data sets must remain in | track-managed space. Topic: MNOTES from the AMDSADMP macro >> Add the following new MNOTE AMDSADMP: REAL=ALL OR REAL=USED NOT SPECIFIED, THE DEFAULT REAL=ALL WILL BE USED. Explanation: Either the REAL keyword was not specified or it was not specified correctly. REAL=ALL is the default. Severity Code: 0 Topic: Syntax of the AMDSADMP macro >> Add the following to the syntax diagram AMDSADMP ,IPL={Tunit|Dunit|DSYSDA} ... | ,REAL={ALL|USED} ... ,ADDSUMM=('options') >> Add the following explanation | REAL={ALL|USED} ___ | Indicates which real storage should be dumped. Specify | USED to dump real storage which is being used at the | time of the dump. Specify ALL to dump all real storage | (used and unused). ALL is the default. Topic: Examples of Coding the AMDSADMP Macro The following examples show how to code the AMDSADMP macro to create various kinds of stand-alone dump programs. Following shows the AMDSADMP macro coded without explicitly specified parameters to generate a direct access resident dump program. The defaults are: IPL=DSYSDA VOLSER=SADUMP ULABEL=NOPURGE CONSOLE=(01F,3278) SYSUT=SYSDA OUTPUT=T282 MSG=ALL MINASID=ALL COMPACT=YES REUSEDS=CHOICE DDSPROMPT=NO | REAL=ALL DUMP1 AMDSADMP >> Add the following in the list of defaults for the rest examples that follow above example. | REAL=ALL Topic: Using the DUMP or ADDSUMM keyword to request additional storage or address spaces You can request that stand-alone dump dump additional storage or additional address spaces in two ways: . Specifying DUMP options or ADDSUMM options on the AMDSADMP macro. As the following example show, specify the dump tailoring options described in "Dump tailoring options" within parentheses and single quotation marks as the value of the DUMP keyword on the AMDSADMP macro. DUMP=('SP(5,37,18) IN ASID('JES3')') DUMP=('RANGE(0:1000000) IN ASID(1)') DUMP=('DATASPACES OF ASID('DUMPSRV')') | DUMP=('SADMPNO IN ASID('IOSAS')') ... Topic: Specifying additional dump options at run time By coding the PROMPT keyword on the AMDSADMP macro, you can have Stand-alone dump prompt the operator to dump additional storage or specify additional address spaces to be dumped as part of summary phase. When you code PROMPT, and the virtual storage dump program gets control, stand-alone dump issues the AMD059D message: AMD059D ENTER DUMP OR SET OR 'ADDSUMM' WITH OPTIONS, LIST OR END The operator can respond with one of the following . DUMP followed by dump options. In this case, the = after DUMP is optional. See "Dump tailoring options" for the possible dump options. |. SET followed by MINASID or REAL options. ... Topic: Dump tailoring options: You can specify the dump tailoring options in one or all of the following ways: . On the DUMP keyword of the AMDSADMP macro. . On the ADDSUMM keyword of the AMDSADMP macro. . By the operator in reply to message AMD059D at run time. Following is a list of dump tailoring options you can specify. For a complete explanation of the options, see "Explanation of dump tailoring options". | {dump-spec-list|SET MINASID{ALL|PHYSIN}|SET REAL(ALL|USED)| | ADDSUMM addsumm-spec-list|LIST|END} dump-spec-list is one or more of the following: . range-spec-list IN ASID (address-space-list) ALSO... . DATASPACES OF domain-spec-list ... . DSP OF domain-spec-list ... . PAGETABLES OF DATASPACES range-spec-list is one or more of the following: - SP(subpool-list) - RANGE(address-range-list) - LSQA - HIGH VIRTUAL | - SADMPNO subpool-list is one of the following: ... Use the following guidelines when specifying values in your dump tailoring options: . High Virtual cannot be used by itself; specify additional keywords. | . SADMPNO cannot be used by itself; specify additional | keywords. . address is a hexadecimal number from 0 to X'7FFFFFFF'. ... Explanation of dump tailoring options: This section provides an explanation for each of the dump tailoring options. RANGE(xxxxxxxx:yyyyyyyy,xxxxxxxx:yyyyyyyy...) Specifies one or more ranges of storage that you want dumped. xxx and yyy are hexadecimal addresses from 0 to X'7FFFFFFF'. ... HIGH VIRTUAL Causes Stand-alone dump to dump all allocated paged out | storage above 2G. This applies to storage that was not | being excluded due to SADMP=NO specification. See | SADMPNO option below for more details. | | | SADMPNO | Causes Stand-alone dump to dump memory objects created | with SADMP=NO in specified address space(s). See IARV64 | in z/OS MVS Programming: Authorized Assemble Services | Reference,EDT-IXG, manual for details. ... Other examples of valid specifications: DUMP SP(0:7,15),RANGE(0:10000000) IN ASID(SYSKEY),ASID(8) DU (SP(0 TO 7 OR 15),SP(255)) IN AS('TCAM') DUMP RANGE(ALL) IN ASID(1) ALSO SP(0) IN ASID(SYSKEY,8) DU DAT OF AS(ALL) DUMP (SP(0:127) IN ASID('GENER') ALSO SP(0) IN ASID('IMS')) DUMP LSQA IN AS(MYJOB,14) DU SP(128),LS IN ASID(C,PHYSIN) DUMP DATASPACES OF ASID(MYJOB??) DUMP DATASPACES OF ASID(MY*) DUMP HIGH VIRTUAL IN ASID(C) ADDSUMM ASID(3F),ASID('DEBBIE') ADDSUMM ASID('MYDB*',40,46:48) AD AS('MYJOB?'),AS(26,REPORT) | DUMP SADMPNO IN ASID('DUMPSRV') | DUMP SADMPNO IN ASID(5,6,'XCFAS') z/OS MVS Dump Output Messages, SA23-1378 Chapter: BLS messages >> Add new message BLS18257I | BLS18257I MERGE SEQUENCE NUMBER GAP DETECTED | | Explanation: | If this message is issued during dump initialization, | the data set being initialized is, or originated from, | a Stand-alone dump multivolume data set which was not | copied using COPYDUMP. Stand-alone dump multivolume | data sets should always be copied using COPYDUMP | before doing any other processing. COPYDUMP merges | the multivolume data set back into logical dumping | order, which improves the performance of subsequent | IPCS processing. | | If this message is issued by COPYDUMP, a | multivolume Stand-alone dump data set is being copied, | but some of the volumes are not included. | | System action: IPCS continues processing the subcommand. | | User response: Use COPYDUMP to copy the original Stand- | alone dump multivolume data set, making sure that all | volumes are included, either via the catalog, or via | VOL=SER=(vol1,vol2,....). | | Source: Interactive Problem Control System (IPCS) KEYWORDS: E2964/K D/T2964
APAR Information
APAR number
OA44443
Reported component name
AMDSADMP
Reported component ID
5752SC115
Reported release
790
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Serviceability /
Xsystem
Submitted date
2014-02-11
Closed date
2015-09-15
Last modified date
2015-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA79018 UA79022
Modules/Macros
AMDSACCT AMDSACCW AMDSADAP AMDSADER AMDSADMP AMDSADM2 AMDSAEDR AMDSAIDD AMDSAIOI AMDSAMDM AMDSAODP AMDSAPGE AMDSAPMT AMDSAPRS AMDSARDX AMDSARSX AMDSASIO AMDSAUCB BLSRCOPY BLSRDRPX BLSRDUIN
| GA32090500 | SA23137800 |
Fix information
Fixed component name
AMDSADMP
Fixed component ID
5752SC115
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 October 2015